Pale Moon 29 x64 and webcomponents.

RMK99 · Unread post by **RMK99** » 2020-06-12, 20:05

Hi.

When Pale Moon will work correct on youtube when dom.webcomponents.enabled is enabled ?

dom.webcomponents.enabled is enabled > works only movies other elements is grey (unloads).

dom.webcomponents.enabled is disabled > youtube works correct.

New Tobin Paradigm · Unread post by **New Tobin Paradigm** » 2020-06-12, 20:23

When it is done and not before.

Unread post by **Sajadi** » 2020-06-13, 12:38

RMK99 wrote: ↑
2020-06-12, 20:05
When Pale Moon will work correct on youtube when dom.webcomponents.enabled is enabled ?

You want to get the job done (or faster)?

In that case i suggest to you that you start with coding help or doing research so the guys who implement know how to fix what is left to fix or you go and find people who can do that! This is a highly complex issue which puts towards the involved people an incredible and highly difficult task who try to get the job done - Complaining is just leading nowhere - especially when it is known that this issue has a special complexity degree!

Some resources which enables you to do one or more of that... Coding boards, Irc channels, newsgroups.

Moonraker · Unread post by **Moonraker** » 2020-07-15, 08:32

@sajadi
Most users on here are not coders,You give the advice but are you actually following it yourself..?...so what contribution to webcomponents sajadi have you actually added yourself..?.Just curious.

Unread post by **adesh** » 2020-07-15, 11:17

Off-topic:
And why are you bumping this without adding anything useful to the discussion?
I think there's going to be a fight. Get prepared.

Unread post by **Moonchild** » 2020-07-15, 11:52

Especially for Moonraker, who thinks that only devs are allowed to post generic advice about development:

You want to get the job done (or faster)?

In that case i suggest to you that you start with coding help or doing research so the guys who implement know how to fix what is left to fix or you go and find people who can do that! This is a highly complex issue which puts towards the involved people an incredible and highly difficult task who try to get the job done - Complaining is just leading nowhere - especially when it is known that this issue has a special complexity degree!

Some resources which enables you to do one or more of that... Coding boards, Irc channels, newsgroups.
Source

samlarson · Unread post by **samlarson** » 2020-09-11, 09:41

Hi.

When Pale Moon will work correct on youtube when dom.webcomponents.enabled is enabled ?

dom.webcomponents.enabled is enabled > works only movies other elements is grey (unloads).

dom.webcomponents.enabled is disabled > youtube works correct.

according to this thread, viewtopic.php?f=3&t=23566 youtube could stop supporting browser every day now, or am I wrong?

Goodydino · Unread post by **Goodydino** » 2020-09-11, 16:55

I do not see dom.webcomponents in about:config. That must be something you have to add to use it. For what do you need it?

Unread post by **Moonchild** » 2020-09-11, 16:59

Goodydino wrote: ↑
2020-09-11, 16:55
I do not see dom.webcomponents in about:config. That must be something you have to add to use it. For what do you need it?

Adding the pref to Pale Moon releases that don't have it present in about:config will do absolutely nothing.

Lurker_01 · Unread post by **Lurker_01** » 2020-09-11, 22:43

Moonchild wrote: ↑
2020-09-11, 16:59
Adding the pref to Pale Moon releases that don't have it present in about:config will do absolutely nothing.

Off-topic:
Unless it is a hidden pref, and there are still some of those that exist...
edit: or is a new user-agent override, but generally, yes

Unread post by **Moonchild** » 2020-09-11, 22:54

Why are you generalizing after I already said it does nothing? it's NOT a hidden pref, it was explicitly removed from releases to prevent people from enabling broken and incomplete webcomponent support thinking it might help them (and then piling on the threads on the forum that "it doesn't work").

ebene · Unread post by **ebene** » 2020-09-13, 11:41

I hope it's acceptable that I ask this question in this thread, as it also directly relates to WebComponents and their future implementation - if not, I apologize and will keep it in mind for future questions, should they become necessary.

Will it be possible to disable the browser's usage of WebComponents, similarly to how e.g. WebAssembly is handled in the browser preferences? From what I understand, the implementation of WebComponents requires more browser-/engine-internal rewrites, so I understand if such a thing is not possible - I ask only because, personally speaking, I am highly unlikely to visit websites that require this functionality, so I am curious as to whether opt-out implementation will be viable or considered for it.

gepus · Unread post by **gepus** » 2020-09-13, 13:01

@ebene
Moonchild already explained the reason why the setting was temporarily removed.

ebene · Unread post by **ebene** » 2020-09-13, 13:24

I'm not referring to the aforementioned setting or its removal; I am very sorry if this was taken as a complaint on this decision (or on anything), as it is very definitely not meant to be one. My question was referring to the eventual full implementation of WebComponents, whenever it is ready for public usage; specifically, whether a setting/preference to disable this technology, similarly to how WASM is handled in the browser's preferences panel, will be included. I apologize for not being more clear on this trivial question, and for any offense caused.

Unread post by **Moonchild** » 2020-09-13, 14:39

No offense taken, at all. Please relax

WebComponents will be behind a preference that will enable or disable the various functions and APIs that are considered part of them. Unfortunately this will not fully disable everything since the compromises made to cater to WebComponents will still be present in the browser engine (and that comes at a cost in terms of performance too). Disabling it will not be equal to "not having it implemented" but for the web side of things it will appear as such and the features can't be used in that case.
We currently have no intention to remove this preference short or long term.

Unread post by **adesh** » 2020-09-13, 14:48

Best would be not to implement it at all. But yeah...

Pentium4User · Unread post by **Pentium4User** » 2020-09-13, 14:52

adesh wrote: ↑
2020-09-13, 14:48
Best would be not to implement it at all. But yeah...

No, because more and more sites use it and it would lead to a less usable browser.

Moonraker · Unread post by **Moonraker** » 2020-09-13, 15:49

Until google comes up with another big shiny new concept...web bundles anyone............?
Dread to think what the googleplex is planning next...World google web will be common parlance in web circles in time to come.

Unread post by **Moonchild** » 2020-09-13, 18:51

Not much else is needed for a fully proprietary web.
Make content protected on the client machine? Check. Shadow DOM will prevent inspection of pages, copying, scanning and archiving.
Make standard content non-standard? Check, CustomElements can redefine every element of a web page, including standard html
Control the distribution? Check, WebBundles will provide packages that can't be filtered or manipulated in transit (because it also includes authenticated delivery)
Also, Check: URLs become meaningless indexes into bundles, no longer open/public addresses

I think most of the puzzle pieces are on the table now.

New Tobin Paradigm · Unread post by **New Tobin Paradigm** » 2020-09-13, 18:58

Welcome. You've got mail.

Pale Moon forum

Pale Moon 29 x64 and webcomponents.

Pale Moon 29 x64 and webcomponents.

Re: Pale Moon 29 x64 and webcomponents.

Re: Pale Moon 29 x64 and webcomponents.

Re: Pale Moon 29 x64 and webcomponents.

Re: Pale Moon 29 x64 and webcomponents.

Re: Pale Moon 29 x64 and webcomponents.

Re: Pale Moon 29 x64 and webcomponents.

Re: Pale Moon 29 x64 and webcomponents.

Re: Pale Moon 29 x64 and webcomponents.

Re: Pale Moon 29 x64 and webcomponents.

Re: Pale Moon 29 x64 and webcomponents.

Re: Pale Moon 29 x64 and webcomponents.

Re: Pale Moon 29 x64 and webcomponents.

Re: Pale Moon 29 x64 and webcomponents.

Re: Pale Moon 29 x64 and webcomponents.

Re: Pale Moon 29 x64 and webcomponents.

Re: Pale Moon 29 x64 and webcomponents.

Re: Pale Moon 29 x64 and webcomponents.

Re: Pale Moon 29 x64 and webcomponents.

Re: Pale Moon 29 x64 and webcomponents.