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
 
Answered
Tecton Extensions and Production/Staging themes

Good Afternoon,

We use a large font theme on our production and staging environments. We noticed that the theme is not applying to tecton SDK extensions. I believe that this is becuase the Tecton extensions are loaded into an iFrame so the CSS is separated. There is mention of look and feel coming through to the tecton side but would things like font-size be taken into account?

2021-10-04 16_29_08-DevTools - digital.visionsfcu.org_visionsfcu_test_01587189_uux.aspx.png

As you can see in the screen shot, the class on the body theme-largefont is what applies the overrides in pre-4.4.0 extensions. Since this tecton extension is served via iFrame, the inner style sheet cannot know that the theme is large font. Is there a way to have our outer large font theme apply to the text inside our tecton extension?

Votes Newest

Answers 3


Dan,

I've gone ahead and created a ticket for this issue. While I can't guarantee a definite date as to when it will be complete, we will try to get it addressed as quickly as possible.

Unfortunately, after looking for an alternative workaround for this issue I haven't been able to come up with anything that would work across multiple themes. Sorry for the inconvenience and difficulty this is causing.


Dan,

Thank you for your patience on this. After looking through the code more in depth, it looks like the --app-font-size variable and the font-size set on the html styles that get passed in to the Tecton environment do not currently have a path to get customized by the theme. Though it definitely should. I do see how, with an update to the UUX codebase, we can get that in place though.

Let me talk to the team in the morning to see if this is something we can prioritize.


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
135 Views
3 Answers
5 years ago
5 years ago
Tags