RESOLVED FIXED 157759
Uncaught Exception: TypeError: null is not an object (evaluating 'event.data.pathComponent.domTreeElement') 
https://bugs.webkit.org/show_bug.cgi?id=157759
Summary Uncaught Exception: TypeError: null is not an object (evaluating 'event.data....
Blaze Burg
Reported 2016-05-16 15:25:58 PDT
------- Auto-generated details: Inspected URL: file:///Users/bburg/repos/webkit-tot/OpenSource/WebKitBuild/Release/WebInspectorUI.framework/Resources/Main.html Loading completed: true Frontend User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_5) AppleWebKit/602.1.33+ (KHTML, like Gecko) Uncaught exceptions: - TypeError: null is not an object (evaluating 'event.data.pathComponent.domTreeElement') (at DOMTreeContentView.js:375:48) ------- * STEPS TO REPRODUCE 1. Go to a random page 2. Start a timeline recording 3. Inspect the inspector, go to the Elements tab 4. Click around on the DOM element path components. 5. > uncaught exception <
Attachments
[PATCH] Proposed Fix (2.83 KB, patch)
2016-05-16 16:36 PDT, Joseph Pecoraro 		no flags
DetailsFormatted DiffDiff
View All Add attachment proposed patch, testcase, etc.
Radar WebKit Bug Importer
Comment 1 2016-05-16 15:27:22 PDT
<rdar://problem/26309427>
Joseph Pecoraro
Comment 2 2016-05-16 15:43:42 PDT
[Error] Assertion Failed _pathComponentSelected (DOMTreeContentView.js:374) dispatch (Object.js:161) dispatchEventToListeners (Object.js:168) _selectElementMouseUp (HierarchicalPathComponent.js:314) _selectElementMouseUp The event.data.pathComponent is null when _selectElementMouseUp triggers on a <select> without a selected index.
Joseph Pecoraro
Comment 3 2016-05-16 16:36:25 PDT
Created attachment 279067 [details] [PATCH] Proposed Fix
WebKit Commit Bot
Comment 4 2016-05-16 21:10:48 PDT
Comment on attachment 279067 [details] [PATCH] Proposed Fix Clearing flags on attachment: 279067 Committed r200995: <http://trac.webkit.org/changeset/200995>
WebKit Commit Bot
Comment 5 2016-05-16 21:10:52 PDT
All reviewed patches have been landed. Closing bug.
Note You need to log in before you can comment on or make changes to this bug.