1296868 - Geometry editor: Moving a relatively positioned element does not update the CSS rules in the "rules" tab

Status: RESOLVED WORKSFORME

(DevTools :: Inspector: Rules, defect)

Description

[brunoais]

"Rules" tab data is not being properly updated if not in view while an element's positioning is being edited using the Geometry editor


Reproduction steps:

1. Go to: https://developer.mozilla.org/en-US/docs/Tools/Page_Inspector/How_to/Reposition_elements_in_the_page
2. Inspect the element selectable with "#wikiArticle>.geckoVersionNote"
3. Add the inline rules "position:relative;top:0;right:0" using the inspector.
4. Change to the "Box Model" tab.
5. Start the geometry editor (clicking on the top-right icon inside the tab).
6. Change the Geometry in some way.
   E.g: Change the "top" to 5px by dragging slightly down in the Geometry editor.
7. Change to the "Rules" tab.
8. The "top" CSS rule does not match the position offset given.
   If the steps above were followed, it should state 0px as it was before and not the 5px as it should be.

Any more information you need, just ask.

Comment 1

[Patrick Brosset <:pbro>]

Which version of Firefox did you test this on? I just tested on Nightly (FF51) and the problem doesn't exist there.

We might have fixed it in the meantime. I remember a bug about this, maybe we should uplift it to FF50 too.
Matteo, do you remember if this was fixed recently?

Comment 2

[Patrick Brosset <:pbro>]

Needinfo for Matteo for my question in comment 1.

Comment 3

[brunoais]

I can confirm the bug doesn't exist in yesterday's nightly build.

Comment 4

[brunoais]

I do remember encountering it in either FF50 or FF51 too.

Comment 5

[Patrick Brosset <:pbro>]

Thanks. Maybe Matteo remembers which bug fixed this and then we'll be able to decide whether we want to uplift it to FF50.

Comment 6

[Matteo Ferretti [:zer0] [:matteo]]

No, I don't. The only bug I remember about that was related to use the wrong object to change the style of the current element with the Geometry Editor, but we fixed that while ago.

Comment 7

[Patrick Brosset <:pbro>]

Ok, thanks. Well, this issue is fixed, so this bug should be closed. I've also just tested with FF50 and it was fixed there too.
If we manage to find out which version it's broken on and which bug fixed it, then we'll be able to fix it on that version too (mozregression can help). But as things stand now, we can't do much.

Comment 8

[brunoais]

When I have some free time, I'll try finding it using mozregression.