server is in Europe, I'm in the US. When attempting to create a new multimedia object in Tridion R5, I click on "schema" to access the drop down and get the following error:

Object doesn't support property or method 'show'

The error also occurs when right clicking on an object The really strange part is that in Europe, the system works properly (although not with my ID). Does Tridion (or can it) use other rights than what is set in Tridion itself? It appears to me that perhaps the call to open the dropdown is accessing a resource that I don't have access to. Is that a possibility, or does anyone else have any ideas?

I don't have access to the server itself, and our support has been sketchy at best, so I'd like to try to point them in the right direction.

@Quovadisqc Thank you for looking into this so intently. It might be worth adding an "IE compatibility" section to the README in a PR.

Here's the problem with option (2): it fundamentally nullifies what preboot is supposed to be doing. Think about it, by the time doc.ReadyState === 'complete', the Angular client app has already been loaded and is starting to bootstrap. This means that preboot has missed the boat on capturing events in the meantime, and for very slow UAs, this could practically be an eternity (in browser-land).

Thus, and I don't like this solution any more than you might, I think option (1) is the only viable option at this point. It might be worth going to the CLI team and requesting a feature for polyfill placement when building an application. Just note that you can automate this yourself by capturing the SSR output and reordering the resultant HTML to place polyfills at the beginning of the HEAD instead of the end of the body.

It might be worth exploring removing the Polyfill-required aspects of the code. I know that the remove can just be converted to parentNode.removeChild, and the Event can just not fire if not available (though we should still convert to CustomEvent since it's easier to polyfill -- as you mentioned in

65). Can you add that to your PR? This particular issue can be resolved by using a standard for loop through the NodeList in EventReplayer instead of creating an iterable using Array.from.

I'll add the first and third workarounds to

62 so that it's incorporated in the next beta and hopefully ease these pains. Apologies for introducing them in the first place, but I guess that's why this is still beta! I'll talk to @jeffwhelpley and @vikerman about possibly adding Travis/Browserstack/Saucelabs support for this repo to ensure cross-browser compatibility in the future.

I am using Madcap Flare 2021 r2 to generate HTML5 output for in-application, context-sensitive help. When the online help is accessed from within the application and a user selects a link within the help topic, a script error appears: Object doesn't support property or method 'startsWith'

The error stems from line 162, char 6833 of MadCapAll.js. It appears that the code is related to the eLearning js, although I am not using the eLearning functionality in my help output.

To correct the issue, I replaced the MadCapAll.js created from Madcap Flare 2021 r2 with a MadCapAll.js file from earlier this year created with Madcap Flare 2021 r1.

Has anyone experienced this issue? If yes, is there a more permanent fix than replacing the MadCapAll.js file in the output?

Thanks!

debdebtig Jr. Propeller Head Posts: 7 Joined: Wed Jan 22, 2014 8:54 am Location: New Hampshire

by debdebtig » Mon Feb 07, 2022 2:46 pm

jmcgill wrote:I am using Madcap Flare 2021 r2 to generate HTML5 output for in-application, context-sensitive help. When the online help is accessed from within the application and a user selects a link within the help topic, a script error appears: Object doesn't support property or method 'startsWith'

The error stems from line 162, char 6833 of MadCapAll.js. It appears that the code is related to the eLearning js, although I am not using the eLearning functionality in my help output.

To correct the issue, I replaced the MadCapAll.js created from Madcap Flare 2021 r2 with a MadCapAll.js file from earlier this year created with Madcap Flare 2021 r1.

Has anyone experienced this issue? If yes, is there a more permanent fix than replacing the MadCapAll.js file in the output?

Thanks!

I just ran into this same error with 2021r3 where we hadn't run into it previously, that I know of. I'm wondering if you did report it to MadCap.

Thanks, Deb

jmcgill Propeller Head Posts: 20 Joined: Thu May 14, 2015 3:35 pm

by jmcgill » Mon Feb 07, 2022 3:01 pm

Yes, I did report it. In the meantime, I have a good/older MadCapAll.js saved in Content\Resources\Scripts\ and the following script in the Post Build-Event for my HTML5 target: