Hey Francisco,

When you say "embedded iframe", are you referring to an <iframe> you're adding to your extension (i.e., So in the end, it's nested <iframe> elements)? That would help us identify if it's a potential issue with our code, or the additional code that you're loading.

Thanks,
Kris

Hello Veda!

Without seeing your code and implementation, it is almost impossible to know what might be going on. I know we looked at Storybook a couple of years ago, but it didn't have great support for Web Components, so we never gave it a second look. If you're trying to create React components that wrap the Tecton components, we have those provided by the Stencil library already (Documented here).

The two things I would check if I did have access to you code is:

1. Check if `custo...

Good morning Maria,

My mistake. I had saw the name TMGSSO and assumed it was an SSO extension using the handler for that workflow. At the moment, we are only able to open an extension in an overpanel from the navigation menu if it is an SSO. With what you're trying to do, there's currently not a way to know if the overpanel has been closed to know that you should navigate them back to the previous route either.

Judging by the video, it looks like an SSO extension, is there a reason yo...

Good afternoon Maria, thanks for your question!

In your extension.py is the RENDER_IN_NEW_WINDOW = False? If so, it should open the SSO in an overpanel while keeping the user on the current page (i.e., dashboard in your example). If you already have that set to False we may need to look at your code to see if there is something in your code causing it to behave differently. If not, it could be something worth looking into on our side.

I just checked on my side using a extension in...

Hey Maria, thanks for reaching out. A couple of questions for you:

1. Do you see any errors in your browser's console that get logged when you try to show the overpanel?
2. Can you tell me what version of UUX you're on (You can view this by typing window.Tecton in your browser's console).

When I tried locally I got an error when I passed {} as the second argument, but if I leave it as null or undefined it works as expected. However, that could be related to configuration on my ...

Good afternoon Edmund,

Currently there is not a way to retrieve the mobile app version. What we can do is mention the window.Tecton object, which identifies the following:

• PLATFORM_VERSION - The version of the platform
• TECTON_PLATFORM_VERSION - The version of q2-tecton-platform running on the platform
• TECTON_SDK_VERSION - The version of the q2-tecton-sdk running in your module
• device - A string indicating the device type (e.g., "phone", "tablet", "desktop")
  ...

Hey David,

Your findings are correct. We have some code that runs in the background of your module, inside that iframe that keeps the height of the iframe in sync with the height of its content. This is in place so that the platform is in charge of scrolling instead of the iframe. As a result, calling window.scrollTo will not do anything.

We do have the scrollToTop capability, and have plans to deliver a scrollTo functionality, but it has not been fully slotted yet. Are you tryi...

Hey Alan,

I pulled down the relevant code onto my machine and wasn't able to reproduce the issue on my iPhone or using the iOS Simulator. Do you know which stack/environment you are running this from when you experience this issue?

Thanks,
Kris

Thanks for the response Alan,

I'm unable to reproduce on my side, using one of my extensions, but another developer experienced something similar a few weeks ago and it turned out to be some kind of CORS issue. However, he's out for a few days, so I'm not able to ping him to see how he fixed it.

Do you have your code pushed up somewhere that I can take a look?

Thanks,
Kris

Good morning Alan,

When you say that the button is showing up gray/black, does it look like one of the attached screenshots? If so, that's indicative that the theme properties are not being loaded and injected into the iframe. A couple of questions to help move forward:

• Can you tell me what mobile devices you are experiencing this issue with?
• Are you experiencing this in the mobile browser or the compiled mobile app?

![Regular](https://community.q2developer.com/upload/files/1676...

Hey Joshua,

Currently, Tecton does provide some out of the box <table> styling which you can view here.

Basically, you'll just want to wrap your table with a <div class="table-wrapper">, then our styling will take care of the rest.

We have just finalized the designs and implementation notes of an official <q2-table> component which will support many features, but that likely wil...

Good afternoon Jared,

I went through our source code because I thought we supported this behavior. However, there are about seven different modals that can display on that page and the one you are asking for is not one of them. We do show a modal with the information you are requesting after the transfer succeeds, but not before submitting it to the server.

We'd hate for you to have to re-create the whole Funds Transfer workflow for this one modal, but at the moment we don't hav...

Good morning Brock,

At this time there isn't a way to detect the theme from within a Tecton extension. The theme is meant to provide you all the styling you would need and not something we recommend writing logic around.

Is there something you're trying to check or change that is based on a particular theme, or perhaps a different problem we can help you solve?

Thanks,
Kris

Hey Kenny,

This is a good question. At the moment, because our React boilerplate doesn't use TypeScript by default, the TectonContext is declared in vanilla JavaScript. Since we can't use Type Annotations in plain JS/X, we are little limited at the time.

If you have already converted your codebase to use TypeScript, doing the following should get you what you want:

// frontend/src/contexts/tecton.ts
import { IActions, ISources } from "q2-tecton-sdk";

const TectonContext = cr...

Hey Lisa,

We don't currently have a recommended font that you should use in this case. If there is a font you have in mind, you are free to utilize it (Given that there are no licensing issues). We do ask that instead of pulling it from a remote CDN that you add the font files directly to your extension and reference it from there.

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 th...