Closed franciscawijaya closed 5 months ago
This checklist is for both Chrome and Firefox: Notes:
Unless specifically stated, the extension had the same effect on both browsers for all websites.
Some websites could not be reached. I manually searched up the website (eg. incontrol clothing) but there are some websites that could not be reached and I could not find the new updated site name
Only one site that has no green ring (yourdictionary) but this site has a green ring on Firefox
Ony two sites, ranker & canon, has a completely green icon (similar to one that we usually see when we go to Washington Post)
[x] https://ama.org
[x] https://nesn.com
[x] https://incontrolclothing.com/ (changed site name to https://www.incontrolclothing.com/)
[x] https://zenefits.com/ (redirected to https://www.trinet.com/)
[x] https://canon.com/ (redirected to a page that state "site took too long to respond" — I manually went to the search bar and look up ‘canon’ which sent me to https://www.usa.canon.com/ ) (complete green)
[x] https://ranker.com/ (complete green)
[x] https://bestbooks.multcolib.org/ (redirected to https://bestbooks.multcolib.org/#view=covers&year=2023)
[x] https://elsevierhealth.com/ (site changed name to https://www.us.elsevierhealth.com/)
[ ] https://lordandtaylor.com/ (site can’t be reached)
[x] https://careers.stelizabeth.com/ (takes a while before the green ring is on in chrome — normal on Firefox)
[x] https://espn.com
[x] https://rpg.net
[x] https://belk.com
[ ] https://apoc.varian.com/ (resource not found)
[x] https://childrens.com/ (takes a while to load the green ring on Chrome — normal on Firefox)
[ ] https://lyncdiscover.irmi.com/ (site can’t be reached)
[ ] https://yourdictionary.com/ (no green ring on Chrome but there is green ring on Firefox)
[x] https://wboy.com
[x] https://afw.com
Attached is the difference of the developer tools' console for Chrome and Firefox for specifically yourdictionary.com
Something notable is on Chrome, the console showed 'Third-party cookie will be blocked' for yourdictionary.com, just like the other websites. However, there is no green ring.
Thanks, @franciscawijaya.
pick 100 random sites from the sample (in the crawler repo) and go to random.org
Well, random.org was for selecting the 100 random sites. :)
I manually searched up the website (eg. incontrol clothing)
What do you mean by "incontrol clothing"?
Which version of OptMeowt did you use? The problem does not seem to be with the current version in the stores but with @OliverWang13's and @Mattm27's mv3 version (branch 350-1 or branch 350-2; @OliverWang13 and @Mattm27, which branch should be used actually?).
What do you mean by "incontrol clothing"?
Some sites changed their name so I just manually searched the updated name
- https://incontrolclothing.com/ (changed site name to https://www.incontrolclothing.com/)
Which version of OptMeowt did you use? The problem does not seem to be with the current version in the stores but with @OliverWang13's and @Mattm27's mv3 version (branch 350-1 or branch 350-2; @OliverWang13 and @Mattm27, which branch should be used actually?).
I loaded unpacked extension for version 4.3.1. I think it was branch 350-1.
URL | Chrome | Firefox |
---|---|---|
url | ✅ | blah |
(Just a sample to modify)
@franciscawijaya will check again using branch 350-5.
Check if that version would work for a good percentage of sites. If not, contact Oliver & Matt.
@franciscawijaya, to get the most recent versions, you can do:
For Firefox: git checkout issue-350-5
.
For Chrome: git checkout 13c0f830011ef9ed72dddf16b16b3e533b7abae7
(the currently latest commit reference).
Then, you can check with git status
that you are on those branches and, if so, follow the normal setup procedure.
All sample sites have green ring! Github on Firefox has green ring; only github on Chrome does not.
Great! Feel free to close any issue once it is done, @franciscawijaya.
Reopening. Seems v5.0.0 for Firefox does not have the green ring and is also not sending the GPC signal properly.
According to the browser developer tools, there currently is an xml parsing error. Potentially concerning the xml syntax in the new updated version?
It is also worth to note that the "cookie-test" being rejected for invalid domain; though, this could maybe come from the underlying xml parsing error.
the xml parsing error seems to be from from Permutive so that actually does not have any correlation with the extension.
As @Mattm27 found, the issue after re-opening was related to the dist manifests being outdated; only the dev manifests were updated after the switch to mv3. v5.0.1 fixes this bug.
Reference: similar to issue #340
Action plan: