Closed
Bug 1406644
Opened 8 years ago
Closed 7 years ago
Javascript not loading on many pages
Categories
(Core :: Networking, defect)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: jwoody11, Unassigned)
Details
Attachments
(1 file)
21.75 KB,
image/jpeg
|
Details |
Javascript fails to load for many pages. It doesn't happen all the time, but quite frequently. Issue isn't found in latest stable release. I've only experienced it in 58. I posed this issue in the forums and have checked all the apparent settings (js enabled, private browsing, extensions, antivirus, proxy, firewall).
Updated•8 years ago
|
Component: JavaScript Engine → DOM
Comment 2•8 years ago
|
||
The script URLs listed in that screenshot are probably all on the tracking protection list(s).
Component: DOM → Tracking Protection
Product: Core → Firefox
(In reply to Andrew Overholt [:overholt] from comment #2)
> The script URLs listed in that screenshot are probably all on the tracking
> protection list(s).
Andrew - any idea what is going on? Why would FF be querying the protection list if tracking protection is not enabled? Typically, if a script is being blocked by TP, then the console would say it's being blocked by TP.
What about the multi-process angle that I posed? I'm not able to recreate the issue with e10 disabled.
Comment 4•8 years ago
|
||
(In reply to Josh from comment #3)
> (In reply to Andrew Overholt [:overholt] from comment #2)
> > The script URLs listed in that screenshot are probably all on the tracking
> > protection list(s).
>
> Andrew - any idea what is going on? Why would FF be querying the protection
> list if tracking protection is not enabled?
Are you sure it's not enabled? Look in about:config for privacy.trackingprotection.enabled and see what the state is.
> What about the multi-process angle that I posed? I'm not able to recreate
> the issue with e10 disabled.
That seems odd. Let's see what people more familiar with tracking protection say.
(In reply to Andrew Overholt [:overholt] from comment #4)
> (In reply to Josh from comment #3)
> > (In reply to Andrew Overholt [:overholt] from comment #2)
> > > The script URLs listed in that screenshot are probably all on the tracking
> > > protection list(s).
> >
> > Andrew - any idea what is going on? Why would FF be querying the protection
> > list if tracking protection is not enabled?
>
> Are you sure it's not enabled? Look in about:config for
> privacy.trackingprotection.enabled and see what the state is.
The value is "False"
>
> > What about the multi-process angle that I posed? I'm not able to recreate
> > the issue with e10 disabled.
>
> That seems odd. Let's see what people more familiar with tracking protection
> say.
Comment 6•7 years ago
|
||
(In reply to Josh from comment #3)
> (In reply to Andrew Overholt [:overholt] from comment #2)
> > The script URLs listed in that screenshot are probably all on the tracking
> > protection list(s).
>
> Andrew - any idea what is going on? Why would FF be querying the protection
> list if tracking protection is not enabled? Typically, if a script is being
> blocked by TP, then the console would say it's being blocked by TP.
All scripts will be examined by tracking protection when privacy.trackingprotection.annotate_channels is enabled (the default) but they will not be blocked unless tracking protection is enabled (privacy.trackingprotection.enabled).
When TP does block something, you're right, it shows up in the console clearly labelled, for example, I see this on this bugzilla page:
The resource at “https://www.google-analytics.com/analytics.js” was blocked because tracking protection is enabled.
Loading failed for the <script> with source “https://www.google-analytics.com/analytics.js”.
Maybe there's something else going on in necko?
Component: Tracking Protection → Networking
Product: Firefox → Core
![]() |
||
Comment 7•7 years ago
|
||
Josh, the fastest way to figure this out is to collect logs. Please see [1] for details, then submit here.
With it, please paste here content of about:support page for a complete information.
Thanks.
[1] https://developer.mozilla.org/en-US/docs/Mozilla/Debugging/HTTP_logging
Flags: needinfo?(jwoody11)
![]() |
||
Updated•7 years ago
|
Whiteboard: ni?2018-01-29
![]() |
||
Updated•7 years ago
|
Whiteboard: ni?2018-01-29
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Resolution: --- → INCOMPLETE
![]() |
||
Updated•7 years ago
|
Flags: needinfo?(jwoody11)
You need to log in
before you can comment on or make changes to this bug.
Description
•