Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

all addressed windows opening in Firefox #7

Open
kbor-maschmi opened this issue May 18, 2021 · 8 comments
Open

all addressed windows opening in Firefox #7

kbor-maschmi opened this issue May 18, 2021 · 8 comments
Assignees

Comments

@kbor-maschmi
Copy link

When using the Firefox browser starting the intro results (most times) in opening all windows/tools that are addressed by the intro-tool.

@matthiasstein
Copy link
Member

The Intro Bundle must open all tools used in the Intro at startup so that the CSS classes are present and can be used by the Intro.

What exactly is the problem? Do the windows close again or do they stay open?

@kbor-maschmi
Copy link
Author

The windows open at startup and stay open. Some buttons are flickering like they are pressed over and over again.

@matthiasstein
Copy link
Member

Does this happen in the sample app as well?
https://demos.conterra.de/mapapps/resources/apps/downloads_intro_4x/index.html?lang=de

If not can you provide your intro configuration?

@matthiasstein matthiasstein self-assigned this May 19, 2021
@matthiasstein
Copy link
Member

Could you check if this new version fixes the error?
https://github.com/conterra/mapapps-intro/releases/tag/2.0.2

@kbor-maschmi
Copy link
Author

The sample app with its default-configuration does not seem to produce the error. When adding several "dummy"-custominfo-buttons (opening a window each) which are also addressed by the intro the error occurs from time to time.

I added our app so you can see how our intro configuration looks like
gda_intro_test.zip

Sadly the new version does not fix the error.

@matthiasstein matthiasstein removed their assignment Nov 3, 2021
@matthiasstein
Copy link
Member

TODO: Einschränkungen dokumentieren

@MartinOver2
Copy link

Raising the timeout value works for me in all Browsers (UserIntro.js):

async(() => {tool.set("active", false); }, 1000);
... and ....

async(() => {
if (appCtx._applicationRootNode.removeClassName !== undefined) { appCtx._applicationRootNode.removeClassName("dn_intro_initializing");
} else {
appCtx._applicationRootNode.className = appCtx._applicationRootNode.className.replace("dn_intro_initializing", "");
}
}, 1100);

@sholtkamp
Copy link
Member

Idea: Make timeout configurable on a case by case basis

@sholtkamp sholtkamp self-assigned this Sep 15, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants