Closed Bug 907412 Opened 11 years ago Closed 11 years ago

Depopulate the customization palette before scaling the customization window upon exiting

Categories

(Firefox :: Toolbars and Customization, defect)

defect
Not set
normal

Tracking

()

RESOLVED FIXED
Firefox 28

People

(Reporter: jaws, Assigned: jaws)

References

Details

(Whiteboard: [Australis:M8])

Attachments

(1 file, 1 obsolete file)

I've noticed on my local builds (which happen to run a bit slower), that the items in the customization palette will adjust positions as the chrome window padding changes, meaning that layout and graphics has to do extra work.

We can hide the palette or remove it from the DOM before beginning the animation.
Assignee: nobody → jaws
Status: NEW → ASSIGNED
Summary: Hide the customization palette before scaling the customization window upon exiting → Depopulate the customization palette before scaling the customization window upon exiting
Attached patch Patch (obsolete) — Splinter Review
This patch makes exiting feel smoother to me. What do you think?
Attachment #793109 - Flags: review?(mconley)
Attached patch Patch v.1Splinter Review
Removed an extra newline.
Attachment #793109 - Attachment is obsolete: true
Attachment #793109 - Flags: review?(mconley)
Attachment #793124 - Flags: review?(mconley)
Comment on attachment 793124 [details] [diff] [review]
Patch v.1

Review of attachment 793124 [details] [diff] [review]:
-----------------------------------------------------------------

LGTM. While here, I noticed those Task.spawns (inside depopulatePalette) don't have an error reporter. Not that I really expect errors, but if you see my point (see also recent fx-dev/m.d.platform discussion), can you file a separate bug about auditing our code so we have at least a basic console.error reporter everywhere? I'm sure add-ons will find ways to break "something". Can be P4 or something along those lines, not really urgent, but we should do it, IMHO.
Attachment #793124 - Flags: review?(mconley) → review+
I was thinking about this more last night... wouldn't it be better for "snappiness" to reverse this patch, and just set the palette to hidden before starting the animation, and then doing the clearing of the palette afterwards?
(In reply to :Gijs Kruitbosch from comment #5)
> I was thinking about this more last night... wouldn't it be better for
> "snappiness" to reverse this patch, and just set the palette to hidden
> before starting the animation, and then doing the clearing of the palette
> afterwards?

That could be better if we think that depopulating the palette requires a noticeable amount of work. I'm not sure if that is the case though.
(In reply to Jared Wein [:jaws] from comment #6)
> (In reply to :Gijs Kruitbosch from comment #5)
> > I was thinking about this more last night... wouldn't it be better for
> > "snappiness" to reverse this patch, and just set the palette to hidden
> > before starting the animation, and then doing the clearing of the palette
> > afterwards?
> 
> That could be better if we think that depopulating the palette requires a
> noticeable amount of work. I'm not sure if that is the case though.

When moving a lot of items to the palette, I can visually see it clearing before the transition starts. :-(
Blocks: 912351
https://hg.mozilla.org/mozilla-central/rev/237d2879d89d
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Whiteboard: [Australis:M8][fixed-in-ux] → [Australis:M8]
Target Milestone: --- → Firefox 28
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: