32.1.0 beta with Google WebComponents

Talk about code development, features, specific bugs, enhancements, patches, and similar things.
Forum rules
Please keep everything here strictly on-topic.
This board is meant for Pale Moon source code development related subjects only like code snippets, patches, specific bugs, git, the repositories, etc.

This is not for tech support! Please do not post tech support questions in the "Development" board!
Please make sure not to use this board for support questions. Please post issues with specific websites, extensions, etc. in the relevant boards for those topics.

Please keep things on-topic as this forum will be used for reference for Pale Moon development. Expect topics that aren't relevant as such to be moved or deleted.
User avatar
Moonchild
Pale Moon guru
Pale Moon guru
Posts: 35475
Joined: 2011-08-28, 17:27
Location: Motala, SE
Contact:

Re: 32.1.0 beta with Google WebComponents

Unread post by Moonchild » 2023-03-01, 22:38

FranklinDM wrote:
2023-03-01, 22:21
Also @Moonchild, you didn't set the dom.getRootNode.enabled pref to true in the beta, which is required in some sites that use WC and is not implied by dom.webcomponents.enabled.
You're absolutely correct. that one completely slipped my mind and should be enabled, period.
"Sometimes, the best way to get what you want is to be a good person." -- Louis Rossmann
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite

User avatar
moonbat
Knows the dark side
Knows the dark side
Posts: 4942
Joined: 2015-12-09, 15:45
Contact:

Re: 32.1.0 beta with Google WebComponents

Unread post by moonbat » 2023-03-02, 00:47

Not to play party pooper but anyone who's unfamiliar with using beta software and is rushing to try this out just so they can get Github/Odysee etc running should pay close attention to this part lest they again come complaining about broken profiles.
Moonchild wrote:
2023-03-01, 15:09
Note: This is beta branded and does NOT come with an automatic updater, and should be considered unstable. Back up your profile if you use your main installation for it (e.g. from the 7z). Use the portable if you want an easy run-and-try separate from your main profile on a blank slate.
"One hosts to look them up, one DNS to find them and in the darkness BIND them."

Image
Linux Mint 21 Xfce x64 on HP i5-5200 laptop, 12 GB RAM.
AutoPageColor|PermissionsPlus|PMPlayer|Pure URL|RecordRewind|TextFX

User avatar
andyprough
Astronaut
Astronaut
Posts: 701
Joined: 2020-05-31, 04:33

Re: 32.1.0 beta with Google WebComponents

Unread post by andyprough » 2023-03-02, 04:11

moonbat wrote:
2023-03-02, 00:47
rushing to try this out just so they can get Github/Odysee etc running
Since this is addressing my post in part, I'll just say in my defense that I don't do Facebook or Google-anything or anime, so I'm kind of limited as a tester. Most of my sites just work. Github and Linkedin and Odysee is about all I could think of.

As far as the warning about broken profiles, I re-install fairly frequently and don't use but a handful of extensions. So even though I am doing this on a fresh profile, if anything were to ever break I wouldn't be upset.

User avatar
moonbat
Knows the dark side
Knows the dark side
Posts: 4942
Joined: 2015-12-09, 15:45
Contact:

Re: 32.1.0 beta with Google WebComponents

Unread post by moonbat » 2023-03-02, 04:14

andyprough wrote:
2023-03-02, 04:11
So even though I am doing this on a fresh profile, if anything were to ever break I wouldn't be upset.
I use TMP so I keep about:profiles pinned, and can instantly launch a separate fresh profile to test any broken sites on the regular build.
"One hosts to look them up, one DNS to find them and in the darkness BIND them."

Image
Linux Mint 21 Xfce x64 on HP i5-5200 laptop, 12 GB RAM.
AutoPageColor|PermissionsPlus|PMPlayer|Pure URL|RecordRewind|TextFX

Enobarbous
Apollo supporter
Apollo supporter
Posts: 49
Joined: 2022-12-06, 17:44

Re: 32.1.0 beta with Google WebComponents

Unread post by Enobarbous » 2023-03-02, 10:00

I tested it a little bit on win7. In general, it works well enough and so far no problems have been noticed.

Suggestions:
- enable performanceObserver by default. This is needed for github (because it can now be used without palefill) and a few other sites.
- remove useragent for yotube (Mozilla/5.0 (%OS_SLICE% rv:68.9) Gecko/20100101 Firefox/68.9). I had to replace it with an agent from actual chrome (Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/110.0.0.0 Safari/537.36) to notice some (slight) performance improvement (but it is still there)
Off-topic:
desctop_polymer.js is 9.67mb... What kind of performance can we even talk about? :?
I am sorry for the use of auto-translator to post

User avatar
Moonchild
Pale Moon guru
Pale Moon guru
Posts: 35475
Joined: 2011-08-28, 17:27
Location: Motala, SE
Contact:

Re: 32.1.0 beta with Google WebComponents

Unread post by Moonchild » 2023-03-02, 10:42

Enobarbous wrote:
2023-03-02, 10:00
enable performanceObserver by default. This is needed for github (because it can now be used without palefill) and a few other sites.
I'd rather not do this, because it is a massive privacy footgun as it's being abused everywhere for creating navigation and browsing profiles by data collectors. measuring performance like page load times and specific timings of navigation elements and what not should only be used by web developers, not be on-by-default for normal consume-browsing.
Enobarbous wrote:
2023-03-02, 10:00
remove useragent for yotube
Ah an illogical placement of a define (thanks, T) defaults it to 68.9 when overridden in the include file. bah. I'll fix that.
"Sometimes, the best way to get what you want is to be a good person." -- Louis Rossmann
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite

Enobarbous
Apollo supporter
Apollo supporter
Posts: 49
Joined: 2022-12-06, 17:44

Re: 32.1.0 beta with Google WebComponents

Unread post by Enobarbous » 2023-03-02, 10:58

Moonchild wrote:
2023-03-02, 10:42
I'd rather not do this, because it is a massive privacy footgun as it's being abused everywhere for creating navigation and browsing profiles by data collectors.
I can't fully agree, but your position is understandable.
In that case, maybe should add this information to the faq and/or release notes and let each user decide for himself? Privacy vs web-compatibility is an old question...
I am sorry for the use of auto-translator to post

User avatar
Moonchild
Pale Moon guru
Pale Moon guru
Posts: 35475
Joined: 2011-08-28, 17:27
Location: Motala, SE
Contact:

Re: 32.1.0 beta with Google WebComponents

Unread post by Moonchild » 2023-03-02, 11:19

Enobarbous wrote:
2023-03-02, 10:58
Privacy vs web-compatibility is an old question...
Actually, it isn't. Privacy versus security is the age-old question, but versus web compatibility is something pretty recent.
No matter how much you find GitHub to be important to your use, enabling this by default will impact everyone on all sites with the proliferation of user profiling in the oodles of JS everywhere. I'm just not going to suddenly make the browser toss everything out the window and "be compatible at all costs". Websites simply should not be using these APIs in their user-facing workflow and if they do it's going to be a problem that will really have all reason to push back against.
So, if you feel you need it, enable at your own risk or peril.
"Sometimes, the best way to get what you want is to be a good person." -- Louis Rossmann
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite

vannilla
Moon Magic practitioner
Moon Magic practitioner
Posts: 2183
Joined: 2018-05-05, 13:29

Re: 32.1.0 beta with Google WebComponents

Unread post by vannilla » 2023-03-02, 13:10

I was running through the MDN tutorial on custom elements and found this one which partially breaks: https://mdn.github.io/web-components-ex ... tylesheet/

Apparently it's because it tries to load the stylesheet with a <link> inside the shadow DOM.
I don't know how new this feature is (i.e. it might be something in draft and yet to be used by frameworks) but I thought I'd report it here.

User avatar
jobbautista9
Keeps coming back
Keeps coming back
Posts: 782
Joined: 2020-11-03, 06:47
Location: Philippines
Contact:

Re: 32.1.0 beta with Google WebComponents

Unread post by jobbautista9 » 2023-03-02, 13:29

Is it just me or am I getting a 403 with the download link? http://testserver.palemoon.org/32-beta/
Image

merry mimas

XUL add-ons developer. You can find a list of add-ons I manage at http://rw.rs/~job/software.html.

Mima avatar by 絵虎. Pixiv post: https://www.pixiv.net/en/artworks/15431817

Image

User avatar
Kris_88
Keeps coming back
Keeps coming back
Posts: 933
Joined: 2021-01-26, 11:18

Re: 32.1.0 beta with Google WebComponents

Unread post by Kris_88 » 2023-03-02, 13:30

I am too...
403 error

User avatar
Kris_88
Keeps coming back
Keeps coming back
Posts: 933
Joined: 2021-01-26, 11:18

Re: 32.1.0 beta with Google WebComponents

Unread post by Kris_88 » 2023-03-02, 13:32


User avatar
Moonchild
Pale Moon guru
Pale Moon guru
Posts: 35475
Joined: 2011-08-28, 17:27
Location: Motala, SE
Contact:

Re: 32.1.0 beta with Google WebComponents

Unread post by Moonchild » 2023-03-02, 13:44

yes, https required.

EDIT: just in case it's needed I've also enabled access on http now.
"Sometimes, the best way to get what you want is to be a good person." -- Louis Rossmann
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite

User avatar
FranklinDM
Add-ons Team
Add-ons Team
Posts: 575
Joined: 2017-01-14, 02:40
Location: Philippines
Contact:

Re: 32.1.0 beta with Google WebComponents

Unread post by FranklinDM » 2023-03-02, 14:04

vannilla wrote:
2023-03-02, 13:10
Apparently it's because it tries to load the stylesheet with a <link> inside the shadow DOM.
Likely bug #1410578. It's already in the list in Issue #2135 (UXP).

User avatar
jobbautista9
Keeps coming back
Keeps coming back
Posts: 782
Joined: 2020-11-03, 06:47
Location: Philippines
Contact:

Re: 32.1.0 beta with Google WebComponents

Unread post by jobbautista9 » 2023-03-02, 14:11

Moonchild wrote:
2023-03-02, 13:44
yes, https required.
Ah, so that's why. I have my own Greasemonkey script which I named "https-nowhere" which turns https links that are not of the same host as the current one into http links, which is why I got the http version instead. Definitely a PEBCAK for me. XD
Image

merry mimas

XUL add-ons developer. You can find a list of add-ons I manage at http://rw.rs/~job/software.html.

Mima avatar by 絵虎. Pixiv post: https://www.pixiv.net/en/artworks/15431817

Image

Michaell
Lunatic
Lunatic
Posts: 282
Joined: 2018-05-26, 18:13

Re: 32.1.0 beta with Google WebComponents

Unread post by Michaell » 2023-03-02, 18:01

Does the new stuff you're adding have any privacy implications, like making connections to google services or enable other additional 3rd party requests?

I should have everything blocked by default, but knowing what to watch for, if anything, would help. I've been mostly running the current and earlier versions with web components enabled (and Palefill) and haven't noticed anything from that. I'm using the beta now (no Palefill) and no problems so far.
Win10home(1709), PM33.0.0-portable as of Feb 1, '24

User avatar
Mæstro
Lunatic
Lunatic
Posts: 463
Joined: 2019-08-13, 00:30
Location: Casumia

Re: 32.1.0 beta with Google WebComponents

Unread post by Mæstro » 2023-03-02, 18:12

Has bug 1691 been treated in this beta? MangaDex offers a test site.
Browser: Pale Moon (Pusser’s repository for Debian)
Operating System: Linux Mint Debian Edition 4 (amd64)
※Receiving Debian 10 LTS security upgrades
Hardware: HP Pavilion DV6-7010 (1400 MHz, 6 GB)
Formerly user TheRealMaestro: æsc is the best letter.

User avatar
sidology
Moon lover
Moon lover
Posts: 79
Joined: 2021-12-04, 22:07

Re: 32.1.0 beta with Google WebComponents

Unread post by sidology » 2023-03-02, 18:26

Mæstro wrote:
2023-03-02, 18:12
Has bug 1691 been treated in this beta?
No. It says "Open", which means it's not treated.

vannilla
Moon Magic practitioner
Moon Magic practitioner
Posts: 2183
Joined: 2018-05-05, 13:29

Re: 32.1.0 beta with Google WebComponents

Unread post by vannilla » 2023-03-02, 19:28

Michaell wrote:
2023-03-02, 18:01
Does the new stuff you're adding have any privacy implications, like making connections to google services or enable other additional 3rd party requests?
No connections are made whatsoever, unless the website you are visiting is programmed to do so.
Google is always mentioned when talking about Web Components and Custom Elements because everything about this technology comes from there.

User avatar
Moonchild
Pale Moon guru
Pale Moon guru
Posts: 35475
Joined: 2011-08-28, 17:27
Location: Motala, SE
Contact:

Re: 32.1.0 beta with Google WebComponents

Unread post by Moonchild » 2023-03-02, 21:03

Michaell wrote:
2023-03-02, 18:01
Does the new stuff you're adding have any privacy implications, like making connections to google services or enable other additional 3rd party requests?
No privacy implications whatsoever. Google WebComponents is a slew of technologies and APIs that have their roots in Google, but it is not a "Google service" or what not. All of this is client-side (i.e. in the browser) parsing and processing of specific types of scripting, document parsing, the document object model, and layout.
"Sometimes, the best way to get what you want is to be a good person." -- Louis Rossmann
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite

Locked