Minor changes, formatting

[shaunbharat]

No description provided.

[MarketingPip]

@shaunbharat - hey Shaun! Hope all is well, great work as always. Too be honest I was maybe going to tag you into another repo to see if you were willing to improve the grammar etc. If willing do let me know, I think there is a couple under
https://github.com/MarketingPipeline that might need reviewed if you are willing,

[shaunbharat]

@MarketingPip sure! I can do that, just tell me which repositories need attention

[MarketingPip]

@shaunbharat I will add you into a private repo! Expect an invite! 👍

As well can I ask if you had any luck with the documentation (Markdown Example) properly rendering on your mobile device? And if so which device are you using & version?

[shaunbharat]

The page at github.com/DarkenLM/Markdown-Tag/index.html renders fine on my Samsung Galaxy S22+

[MarketingPip]

The page at github.com/DarkenLM/Markdown-Tag/index.html renders fine on my Samsung Galaxy S22+

Thank you for confirming! @shaunbharat

@DarkenLM - no chance you have any insight on why things work properly with the current version of the script on older version of iOS vs the newer version?

By chance is there not browser compatibility with custom web components on older versions of Safari that I'm not aware of?

Hoping we can address this obviously as I would / could see this being obviously and issue for lots of users that are in same predicament as me with and older phone.

[DarkenLM]

@DarkenLM - no chance you have any insight on why things work properly with the current version of the script on older version of iOS vs the newer version?

According to this page, Safari for iOS 3.2 to 10.2 are simply not supported. The problem with this is simply asshole design from Apple (whose fortunately the EU decided to obliterate) to not follow any web standards because screw our customers.

By chance is there not browser compatibility with custom web components on older versions of Safari that I'm not aware of?

The only way I think we can support iOS partially is using the WebComponents Polyfill, that unfortunately, cannot provide all the functionality. I think my webcomponent is mostly compatible with it, but detecting when a browser is a specific versions is hard. Bowser seems to correctly detect my browser, but as I can't test on any iOS, I can't tell for sure.

[MarketingPip]

@DarkenLM - no chance you have any insight on why things work properly with the current version of the script on older version of iOS vs the newer version?

According to this page, Safari for iOS 3.2 to 10.2 are simply not supported. The problem with this is simply asshole design from Apple (whose fortunately the EU decided to obliterate) to not follow any web standards because screw our customers.

By chance is there not browser compatibility with custom web components on older versions of Safari that I'm not aware of?

The only way I think we can support iOS partially is using the WebComponents Polyfill, that unfortunately, cannot provide all the functionality. I think my webcomponent is mostly compatible with it, but detecting when a browser is a specific versions is hard. Bowser seems to correctly detect my browser, but as I can't test on any iOS, I can't tell for sure.

@DarkenLM - by chance could you list the features you think would not possibly work? It might sound stupid but just curious if some of them will work in the current version. Not that we are going to use it obviously, but for further understanding of limits of WebComponents etc.

Keep in mind - another web-component under github.com/MarketingPipeline render's fine on my iOS device (older iOS version) as well said - so does the current version of Markdown-Tag (the current non web-component version)

But I am not familiar if Lit has more advantages then Polyfill but I have been pointed in that direction lately when discussing web-components.