A TabSelect of tab B right after a TabClose of tab A will (at least on some occasions) cause a TabAttrModified to be sent to tab A. I would think that after a TabClose is sent for a tab, no other events should be sent for that tab. See bug 596279, particularly the call stack, for more info.
Assignee: nobody → dao
OS: Mac OS X → All
Hardware: x86 → All
Version: unspecified → Trunk
Created attachment 476744 [details] [diff] [review] patch
Attachment #476744 - Flags: review?(gavin.sharp)
Attachment #476744 - Flags: review?(gavin.sharp) → review+
Attachment #476744 - Flags: approval2.0+
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 4.0b7
You need to log in before you can comment on or make changes to this bug.