Closed Bug 1351685 Opened 8 years ago Closed 7 years ago

Remove the box model from the computed view

Categories

(DevTools :: Inspector, enhancement, P3)

enhancement

Tracking

(firefox61 fixed)

RESOLVED FIXED
Firefox 61
Tracking Status
firefox61 --- fixed

People

(Reporter: jdescottes, Assigned: gl)

References

(Blocks 1 open bug)

Details

Attachments

(2 files)

Title says most of it. We currently have duplicated box-model widget in both the layout & computed views. It's confusing, users can't easily tell where they are since both panels look the same etc... Does anyone share this concern? Do we plan to take a decision here before shipping the layout panel? I can see a few options: - simply remove the box-model widget from the computed view - hide the box-model widget from the computed view if and only if the layout panel is enabled
As I recall, the original idea was to have a simple box-model widget in the computed-view, something you can quickly look at to find computed values for the margin, border, padding, content. And the layout panel would contain a much more interesting view of it, with more properties, more information, but which would occupy more room too.
Attached image layout_vs_computed_panel.gif (deleted) —
My main issue is that when the devtools are docked to the bottom, both panels look identical at first glance. Here's a GIF to illustrate this. But if I'm the only one finding this confusing, feel free to close!
No, you're not the only one who's confused by the similarity between the two panels :-)
Severity: normal → enhancement
Priority: -- → P3
No longer blocks: 1347964
How about making the box model section in the computed view a link to the layout view ? Something like this: Rules | [Computed] | Layout | Animations --------------------------------------- [ Filter Styles ][ ] Browser styles --------------------------------------- Box model > --------------------------------------- ... Or an infobar like in the Layout panel: (i) The box-model view has moved to the [layout panel] (x)
It was decided for the 3 pane inspector that we would remove the box model from the computed view. https://docs.google.com/document/d/1FDhZp-Qd9u38l14t8eU-hPG54Na7GqbBDFQWraNIyws/edit#
Blocks: 1433716
Component: Developer Tools: Inspector → Developer Tools: Computed Styles Inspector
Summary: [discussion] Should we keep the boxmodel in the computed view when the layout panel is enabled → Remove the box model from the computed view
Assignee: nobody → gl
Status: NEW → ASSIGNED
Comment on attachment 8956687 [details] Bug 1351685 - Remove the box model from the computed view. https://reviewboard.mozilla.org/r/225640/#review231524 Looks good. Please land this only during the 61 cycle, so that it ships with 3-pane.
Attachment #8956687 - Flags: review?(pbrosset) → review+
Pushed by gabriel.luong@gmail.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/57ba784a1cd9 Remove the box model from the computed view. r=pbro
Backout by csabou@mozilla.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/6c1886396b55 Backed out changeset 57ba784a1cd9 for ESlint failure on browser_boxmodel_computed-accordion-state.js
Pushed by gabriel.luong@gmail.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/139930cd68e2 Remove the box model from the computed view. r=pbro
Backout by cbrindusan@mozilla.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/04cb6477bb38 Backed out changeset 139930cd68e2 for xpcshell failures on test_ext_webRequest_responseBody.js CLOSED TREE
Sorry about the previous message, the backout was for devtools failures.
Pushed by gabriel.luong@gmail.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/bae5dd6b9a2a Remove the box model from the computed view. r=pbro
Blocks: 1445153
Backed out for devtools failres on browser_boxmodel_editablemodel.js Log: https://treeherder.mozilla.org/logviewer.html#?job_id=167609905&repo=mozilla-inbound&lineNumber=1800
Backout by nbeleuzu@mozilla.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/961f8637533b Backed out changeset bae5dd6b9a2a for devtools failres on browser_boxmodel_editablemodel.js
For information the test fails because the toolbox is too small and the previous focus the element below the boxmodel. The box model top fields become scrolled out and the click fails. Either: - increase the toolbox height: yield pushPref("devtools.toolbox.footer.height", 500); - ensure the box model container is fully visible let container = boxmodel.document.querySelector(".boxmodel-container"); container.scrollIntoView();
Forgot to mention: the test that fails is testRefocusingOnClick(), not sure exactly which previous test is moving the focus and scrolling out the container, but if you decide to scrollIntoView the boxmodel container, it would probably make sense to do it in each test method.
Flags: needinfo?(gl)
Pushed by gabriel.luong@gmail.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/1d9cd8bb925d Remove the box model from the computed view. r=pbro
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 61
I have reproduced this bug with Nightly 55.0a1 (2017-03-29) on Windows 10, 64 Bit! This bug's fix is verified with latest Nightly! Build ID : 20180419224145 User Agent : Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:61.0) Gecko/20100101 Firefox/61.0
QA Whiteboard: [bugday-20180418]
Product: Firefox → DevTools
Component: Inspector: Computed → Inspector
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: