Examples: query, "exact match", wildcard*, wild?ard, wild*rd
Fuzzy search: cake~ (finds cakes, bake)
Term boost: "red velvet"^4, chocolate^2
Field grouping: tags:(+work -"fun-stuff")
Escape special characters +-&|!(){}[]^"~*?:\ - e.g. \+ \* \!
Range search: properties.timestamp:[1587729413488 TO *] (inclusive), properties.title:{A TO Z}(excluding A and Z)
Combinations: chocolate AND vanilla, chocolate OR vanilla, (chocolate OR vanilla) NOT "vanilla pudding"
Field search: properties.title:"The Title" AND text
 
Unanswered
← Tecton Extensions and Production/Staging themes

Good morning Dan!

The way we pass theming information down in to the iframe is through the use of CSS Custom Properties. We pass in a large number of these to ensure that the styling of the Web Components and other bits match the parent application so that it appears seamless.

As to you question, we currently expose the CSS property/variable --app-font-size, but should also be setting the font-size on the html tag within the iframe. Can you verify whether this is either not taking place or is not the value you expect?

Looking through the code, it is possible a variable needs to get added/updated in the theme stylesheet.

0

Thank you for the update Kristopher! That variable is being set, but to 14px. Our large font theme is setting the body font-size to 18px. Here is a link to our theme css in the next comment (too long).

— Dan Collins   5 years ago
0

https://cdn1.onlineaccess1.com/cdn/depot/5192/981/7bd18ff4409c2ee3ab68fd436700fdd0/assets/theme-largefont-e841ffdb69d6e8bf106b00cced42375a.css
Is there something we should be doing differently to make sure that comes through correctly?

— Dan Collins   5 years ago
31 Views
0 Answers
5 years ago
5 years ago