| Summary: | Web Inspector: DOM tree is missing parts of the DOM tree when remotely inspecting iOS devices | ||||||
|---|---|---|---|---|---|---|---|
| Product: | WebKit | Reporter: | Jeff Johnson <opendarwin> | ||||
| Component: | Web Inspector | Assignee: | Patrick Angle <pangle> | ||||
| Status: | RESOLVED FIXED | ||||||
| Severity: | Normal | CC: | inspector-bugzilla-changes, pangle, webkit-bug-importer | ||||
| Priority: | P2 | Keywords: | InRadar | ||||
| Version: | Safari Technology Preview | ||||||
| Hardware: | iPhone / iPad | ||||||
| OS: | iOS 16 | ||||||
| Attachments: |
|
||||||
|
Description
Jeff Johnson
2022-09-17 08:39:55 PDT
The lack of the "Not found" string next to the search field would suggest we are failing to even perform the search, and the inability to enter element selection mode is most likely related. I wasn't readily able to reproduce, but perhaps the iPadOS version matters – what version of iPadOS is your iPad running? (In reply to Patrick Angle from comment #1) > I wasn't readily able to reproduce, > but perhaps the iPadOS version matters – what version of iPadOS is your iPad > running? I can reproduce with today's beta iPadOS 16.1 (20B5050f) and with the public release iOS 16.0 (20A362) on iPhone. I can't reproduce with the public release iOS 15.7 (19H12) on iPhone. Thank you for the version info. After a bit of experimenting I am able to reproduce so long as I have installed and enabled the "Stop the Madness" extension on the iOS or iPadOS device. It appears Web Inspector is missing a chunk of the DOM tree (that is still being rendered correctly) when I've enabled the extension. I'm going to need to investigate a bit further; I suspect this is not unique to this extension. (In reply to Patrick Angle from comment #4) > Thank you for the version info. After a bit of experimenting I am able to > reproduce so long as I have installed and enabled the "Stop the Madness" > extension on the iOS or iPadOS device. It appears Web Inspector is missing a > chunk of the DOM tree (that is still being rendered correctly) when I've > enabled the extension. I'm going to need to investigate a bit further; I > suspect this is not unique to this extension. I just installed Safari Technology Preview 154, and I can reproduce with all extensions disabled, so I wonder whether having the extension enabled was only a coincidence. (In reply to Jeff Johnson from comment #5) > I just installed Safari Technology Preview 154, and I can reproduce with all > extensions disabled, so I wonder whether having the extension enabled was > only a coincidence. Ah, it now readily reproduces even without any extensions enabled. Not sure what state I was stuck in preventing me from reproducing, but I'm now not stuck in that state. I see the issue too... Thank you for following up! Pull request: https://github.com/WebKit/WebKit/pull/4585 Committed 254744@main (467145024522): <https://commits.webkit.org/254744@main> Reviewed commits have been landed. Closing PR #4585 and removing active labels. |