The Wayback Machine - https://web.archive.org/web/20211021093754/https://github.com/gorhill/uBlock/issues/1646
Skip to content
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

Jump to bottom

Logger inspector sometimes stays blank after loading page #1646

Open
laniakea64 opened this issue May 21, 2016 · 3 comments
Open

Logger inspector sometimes stays blank after loading page #1646

laniakea64 opened this issue May 21, 2016 · 3 comments

Comments

@laniakea64
Copy link

@laniakea64 laniakea64 commented May 21, 2016

Environment:

SeaMonkey (or Firefox 45.1.1esr), new profile
uBlock Origin 1.7.0

Steps for anyone to reproduce the issue

  1. install uBlock Origin
  2. install Mozilla Archive Format (I use version 4.0rc1)
  3. restart SeaMonkey (then close all but one tab)
  4. open uBlock Origin logger, select the inspector
  5. open a MAFF file in the other tab
  6. check the inspector

Alternate steps-to-reproduce:
put these two files up on a server:

<!doctype html>
<link rel="stylesheet" href="hang.php" type="text/css" />

<div>AAAAAAAAAAAAAA</div>
<img src="/some/image.gif" />

hang.php:

<?php while(true) {} ?>

then:

  1. install uBlock Origin, restart SeaMonkey
  2. open the logger
  3. in the other tab, navigate to the html file on the server
  4. in the uBlock Origin logger, open the inspector

Expected results:
DOM of the page loaded in the other tab shows up in the inspector

Actual results:
inspector remains blank, regardless of any (stopping &) reloading the other tab, either from the logger or the browser's buttons.

(Some related discussion at InformAction: https://forums.informaction.com/viewtopic.php?p=83022#p83022 )
@gorhill
Copy link
Owner

@gorhill gorhill commented Sep 11, 2017

It was a once-in-a-while issue, which has never affected the Chromium version of uBO, hence assuming it's not an issue for webext.
@gorhill gorhill closed this Sep 11, 2017
@laniakea64
Copy link
Author

@laniakea64 laniakea64 commented Sep 11, 2017

assuming it's not an issue for webext.

I can reproduce this issue with uBO/webext 1.14.9b0 on Firefox 57.0a1 (2017-09-11). Are you saying you tried the steps-to-reproduce with uBO/webext and got a fully functional logger inspector?
@gorhill
Copy link
Owner

@gorhill gorhill commented Sep 11, 2017 •
edited

Sorry, there was another issue which was the logger not reporting anything right after being opened, I confused the issue here with that one. The issue here is about the inspector specifically.
@gorhill gorhill reopened this Sep 11, 2017
@gorhill gorhill removed the wontfix label Sep 11, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
2 participants
@gorhill @laniakea64