Closed Bug 1619566 Opened 5 years ago Closed 5 years ago

URIError: malformed URI sequence

Categories

(DevTools :: Netmonitor, defect, P1)

defect

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: Honza, Unassigned)

Details

STR:
0) Open DevTools & select the Network panel

  1. Load http://janodvarko.cz/firebug/tests/601/Issue601.htm?test=1%,2+,3+
  2. Select the first request and go to the Params panel. The Network panel goes blank -> BUG

There is an error in the Browser Console

The above error occurred in the <ParamsPanel> component:
    in ParamsPanel
    in VisibilityHandler
    in Unknown (created by Connect(Component))
    in Connect(Component) (created by TabboxPanel)
    in div (created by Panel)
    in Panel (created by TabboxPanel)
    in div (created by Tabs)
    in div (created by Tabs)
    in div (created by Tabs)
    in Tabs (created by Sidebar)
    in Sidebar (created by Tabbar)
    in div (created by Tabbar)
    in Tabbar (created by TabboxPanel)
    in TabboxPanel (created by NetworkDetailsPanel)
    in div (created by NetworkDetailsPanel)
    in NetworkDetailsPanel
    in VisibilityHandler
    in Unknown (created by Connect(Component))
    in Connect(Component) (created by MonitorPanel)
    in div (created by SplitBox)
    in div (created by SplitBox)
    in SplitBox (created by MonitorPanel)
    in div (created by MonitorPanel)
    in MonitorPanel
    in VisibilityHandler
    in Unknown (created by Connect(Component))
    in Connect(Component) (created by App)
    in div (created by DropHarHandler)
    in DropHarHandler (created by App)
    in div (created by App)
    in App
    in VisibilityHandler
    in Unknown (created by Connect(Component))
    in Connect(Component)
    in Provider

Consider adding an error boundary to your tree to customize error handling behavior.
Visit https://fb.me/react-error-boundaries to learn more about error boundaries. react-do
URIError: malformed URI sequence2 request-utils.js:338:14

Honza

False alarm, forgotten patch applied.
Closing

Honza

Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.