-
-
Notifications
You must be signed in to change notification settings - Fork 343
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
(1379148) (WebExtensions) Waterfox Classic with sites such as answers.microsoft.com (Microsoft Answers): document.write does not synchronously modify a document if an extension has content scripts at document_start #856
Comments
This comment has been minimized.
This comment has been minimized.
This now works in 68 Alpha. Any chance the fix can get into the 56 line of builds? Thanks! |
Yep I’ll pull this in from upstream.
…On Thu, 23 May 2019 at 21:30, rebop ***@***.***> wrote:
This now works in 68 Alpha. Any chance the fix can get into the 56 line of
builds? Thanks!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#856>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABECQWCGBVVQUMWXS4LFRETPW35FNANCNFSM4GUKWUKA>
.
|
Thanks so much!
Also, I hope my learnings on 68 on Reddit are helpful. If there is a better
way of posting what I discover, please let me know.
_____
From: Alex Kontos [mailto:[email protected]]
Sent: Thursday, May 23, 2019 1:31 PM
To: MrAlex94/Waterfox
Cc: rebop; Comment
Subject: Re: [MrAlex94/Waterfox] (1379148) (WebExtensions) Waterfox 56 with
sites such as answers.microsoft.com (Microsoft Answers): document.write does
not synchronously modify a document if an extension has content scripts at
document_start (#856)
Yep I'll pull this in from upstream.
On Thu, 23 May 2019 at 21:30, rebop ***@***.***> wrote:
This now works in 68 Alpha. Any chance the fix can get into the 56 line of
builds? Thanks!
-
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#856&
email_token=ABECQWCGCEYXV2S7JRQSYTTPW35FNA5CNFSM4GUKWUKKYY3PNVWWK3TUL52HS4DF
VREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWDMZPQ#issuecomment-495373502>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABECQWCGBVVQUMWXS4LFRETPW
35FNANCNFSM4GUKWUKA>
.
-
You are receiving this because you commented.
Reply to this email directly, view
<#856&
email_token=ADJFPUT3ZXS3TK4BRM6FZJDPW35J3A5CNFSM4GUKWUKKYY3PNVWWK3TUL52HS4DF
VREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWDM4EA#issuecomment-495373840> it
on GitHub, or mute
<https://github.com/notifications/unsubscribe-auth/ADJFPUTJQVRP7JC2J3VCO7TPW
35J3ANCNFSM4GUKWUKA> the thread.
<https://github.com/notifications/beacon/ADJFPUUYBINUPVCSCTWGEGTPW35J3A5CNFS
M4GUKWUKKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWDM4EA
.gif>
|
Surprised this has not yet been pulled in. Still broken in 56.2.12 |
And still not working in 56.2.13. Can we get this one corrected please? Thanks. |
Still not working in 56.2.14. A hopeful reminder to fix this on eplease. |
Fixed in 2019.10 Classic. |
Thanks. Also, please retry an outdated version of Waterfox Classic. Posted without difficulty using outdated home-built Waterfox Classic 56.2.14 (20191007063316) on FreeBSD-CURRENT: Skype and Skype for Business on FreeBSD - Microsoft Community |
So this issue can be closed, just like also #1065 😄. |
Spun off from https://redd.it/akpg72 involving any one of a number of blocking extensions.
Waterfox 56.2.7.1 on Lubuntu with (experimental, featured) Malwarebytes Browser Extension 1.0.32 enabled, but disabled for an affected page:
Broadly disabling protection is not a workaround:
Worked around by disabling the extension:
Observations
Re: openstyles/stylus#100 (comment) under Firefox: Microsoft Answers is broken · Issue #100 · openstyles/stylus I guess that one or two patches will resolve this issue. Just a guess; not enough for a pull request from me (sorry).
Nutshell
Might we get lucky with the one patch that applied on FreeBSD? I wonder.
Thoughts
Whilst we're without a fix for 56 e.g. 56.2.7.1 for Linux, Mac OS X and Windows: I have a hunch that there might be another workaround … if I find another, I'll add a comment.
The text was updated successfully, but these errors were encountered: