[Webkit-unassigned] [Bug 272310] New: Web Inspector: Make more obvious the reload attempts of a Webpage

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Sun Apr 7 17:18:49 PDT 2024


https://bugs.webkit.org/show_bug.cgi?id=272310

            Bug ID: 272310
           Summary: Web Inspector: Make more obvious the reload attempts
                    of a Webpage
           Product: WebKit
           Version: Other
          Hardware: All
                OS: All
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: Web Inspector
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: karlcow at apple.com
                CC: inspector-bugzilla-changes at group.apple.com,
                    rcaliman at apple.com,
                    webkit-bug-importer at group.apple.com

Created attachment 470806

  --> https://bugs.webkit.org/attachment.cgi?id=470806&action=review

testcase

In Bug 17186, the testcase gives the possibility to refresh the page at a regular pace.

Case 1:
  data:text/html,<head><meta http-equiv="refresh" content="5"></head><div>This page refreshes every 5s</div>

This creates error messages consistently across browsers. 
* Safari:  Not allowed to navigate top frame to data URL 'data:text/html,<head><meta%20http-equiv="refresh"%20content="5"></head><div>This%20page%20refreshes%20every%205s</div>'.
* Firefox: Navigation to toplevel data: URI not allowed (Blocked loading of: “data:text/html,<head><meta http-equiv="refresh" co...”) 
* Chrome: Not allowed to navigate top frame to data URL: data:text/html,<head><meta http-equiv="refresh" content="5"></head><div>This page refreshes every 5s</div>

So far so good.

Case 2: 
  Save the test case as a local file
  And then open this file locally aka file:// scheme.
The 3 browsers shows in the Console.log an increment for each reload. 


case 3:
  Load the test case from the URL in this bug report. 
* Safari increment the clock on the "Page Reloaded at <time>" message, but this is not really noticeable
* Firefox creates a new entry in the log for each attempgt
* Chrome increments automatically the counter showing the number of reload attempts.


Probably Safari Web Inspector should make it more obvious that something has changed specifically when this is happening for file://

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20240408/037e8940/attachment-0001.htm>


More information about the webkit-unassigned mailing list