Sounds really inconvenient for platform developers to have DevTools change the layout for them while inspecting. On a cursory look, I see a few places where `getBoxQuads()` is used in the DevTools in such as way as to measure the content on the inspected page: - within a [util for the on the server, `nodeHasSize()`,](https://searchfox.org/mozilla-central/rev/40e889be8ff926e32f7567957f4c316f14f6fbef/devtools/server/actors/inspector/utils.js#195) being called when [filtering the DOM with `standardTreeWalkerFilter()`](https://searchfox.org/mozilla-central/rev/40e889be8ff926e32f7567957f4c316f14f6fbef/devtools/server/actors/inspector/utils.js#120-136) which is then used in the [walker and document-walker](https://searchfox.org/mozilla-central/search?path=&q=standardTreeWalkerFilter). This ends up called when opening the Inspector as part of a node selection/traversal. - within a [util to get adjusted quads](https://searchfox.org/mozilla-central/rev/40e889be8ff926e32f7567957f4c316f14f6fbef/devtools/shared/layout/utils.js#164) for all highlighters (ex: element highlighter, shape path, etc) to account for iframe offsets and zoom levels. This seems important. Without digging too deep, it seems that the node filter used in DOM traversal is most likey to cause the issues because of its use of `getBoxQuads()`. This is part of the code I have little experience with yet. I will ping Patrick and Gabriel for their assessment if we can circumvent or restrict the use of `getBoxQuads()` in that scenario.
Bug 1567310 Comment 1 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Sounds really inconvenient for platform developers to have DevTools change the layout for them while inspecting. On a cursory look, I see a few places where `getBoxQuads()` is used in the DevTools in such as way as to measure the content on the inspected page: - within a [util for the on the server, `nodeHasSize()`,](https://searchfox.org/mozilla-central/rev/40e889be8ff926e32f7567957f4c316f14f6fbef/devtools/server/actors/inspector/utils.js#195) being called when [filtering the DOM with `standardTreeWalkerFilter()`](https://searchfox.org/mozilla-central/rev/40e889be8ff926e32f7567957f4c316f14f6fbef/devtools/server/actors/inspector/utils.js#120-136) which is then used in the [walker and document-walker](https://searchfox.org/mozilla-central/search?path=&q=standardTreeWalkerFilter). This ends up called when opening the Inspector as part of a node selection/traversal. - within a [util to get adjusted quads](https://searchfox.org/mozilla-central/rev/40e889be8ff926e32f7567957f4c316f14f6fbef/devtools/shared/layout/utils.js#164) for all highlighters (ex: element highlighter, shape path, etc) to account for iframe offsets and zoom levels. This seems important enough to keep. Without digging too deep, it seems that the node filter used in DOM traversal is most likey to cause the issues because of its use of `getBoxQuads()`. This is part of the code I have little experience with yet. I will ping Patrick and Gabriel for their assessment if we can circumvent or restrict the use of `getBoxQuads()` in that scenario.
Sounds really inconvenient for platform developers to have DevTools change the layout for them while inspecting. On a cursory look, I see a few places where `getBoxQuads()` is used in the DevTools in such as way as to measure the content on the inspected page: - within a [util for the on the server, `nodeHasSize()`,](https://searchfox.org/mozilla-central/rev/40e889be8ff926e32f7567957f4c316f14f6fbef/devtools/server/actors/inspector/utils.js#195) being called when [filtering the DOM with `standardTreeWalkerFilter()`](https://searchfox.org/mozilla-central/rev/40e889be8ff926e32f7567957f4c316f14f6fbef/devtools/server/actors/inspector/utils.js#120-136) which is then used in the [walker and document-walker](https://searchfox.org/mozilla-central/search?path=&q=standardTreeWalkerFilter). This ends up called when opening the Inspector as part of a node selection/traversal. - within a [util to get adjusted quads](https://searchfox.org/mozilla-central/rev/40e889be8ff926e32f7567957f4c316f14f6fbef/devtools/shared/layout/utils.js#164) for all highlighters (ex: element highlighter, shape path, etc) to account for iframe offsets and zoom levels. This seems important enough to keep. Without digging too deep, it seems that the node filter used in DOM traversal is most likey to cause the issues because of its automatic use of `getBoxQuads()` in the process of node traversal. This is part of the code I have little experience with yet. I will ping Patrick and Gabriel for their assessment if we can circumvent or restrict the use of `getBoxQuads()` in that scenario.
Sounds really inconvenient for platform developers to have DevTools change the layout for them while inspecting. On a cursory look, I see a few places where `getBoxQuads()` is used in the DevTools in such as way as to measure the content on the inspected page: - within a [util for the on the server, `nodeHasSize()`,](https://searchfox.org/mozilla-central/rev/40e889be8ff926e32f7567957f4c316f14f6fbef/devtools/server/actors/inspector/utils.js#195) being called when [filtering the DOM with `standardTreeWalkerFilter()`](https://searchfox.org/mozilla-central/rev/40e889be8ff926e32f7567957f4c316f14f6fbef/devtools/server/actors/inspector/utils.js#120-136) which is then used in the [walker and document-walker](https://searchfox.org/mozilla-central/search?path=&q=standardTreeWalkerFilter). This ends up called when opening the Inspector as part of a node selection/traversal. - within a [util to get adjusted quads](https://searchfox.org/mozilla-central/rev/40e889be8ff926e32f7567957f4c316f14f6fbef/devtools/shared/layout/utils.js#164) for [highlighters](https://searchfox.org/mozilla-central/search?q=getAdjustedQuads&path=) (ex: element highlighter, shape path editor, grid/flex, etc) to account for iframe offsets and zoom levels. This seems important enough to keep. Without digging too deep, it seems that the node filter used in DOM traversal is most likey to cause the issues because of its automatic use of `getBoxQuads()` in the process of node traversal. This is part of the code I have little experience with yet. I will ping Patrick and Gabriel for their assessment if we can circumvent or restrict the use of `getBoxQuads()` in that scenario.
Sounds really inconvenient for platform developers to have DevTools change the layout for them while inspecting. On a cursory look, I see a few places where `getBoxQuads()` is used in the DevTools in such as way as to measure the content on the inspected page: - within a [util on the server, `nodeHasSize()`,](https://searchfox.org/mozilla-central/rev/40e889be8ff926e32f7567957f4c316f14f6fbef/devtools/server/actors/inspector/utils.js#195) being called when [filtering the DOM with `standardTreeWalkerFilter()`](https://searchfox.org/mozilla-central/rev/40e889be8ff926e32f7567957f4c316f14f6fbef/devtools/server/actors/inspector/utils.js#120-136) which is then used in the [walker and document-walker](https://searchfox.org/mozilla-central/search?path=&q=standardTreeWalkerFilter). This ends up called when opening the Inspector as part of a node selection/traversal. - within a [util to get adjusted quads](https://searchfox.org/mozilla-central/rev/40e889be8ff926e32f7567957f4c316f14f6fbef/devtools/shared/layout/utils.js#164) for [highlighters](https://searchfox.org/mozilla-central/search?q=getAdjustedQuads&path=) (ex: element highlighter, shape path editor, grid/flex, etc) to account for iframe offsets and zoom levels. This seems important enough to keep. Without digging too deep, it seems that the node filter used in DOM traversal is most likey to cause the issues because of its automatic use of `getBoxQuads()` in the process of node traversal. This is part of the code I have little experience with yet. I will ping Patrick and Gabriel for their assessment if we can circumvent or restrict the use of `getBoxQuads()` in that scenario.