Reviews in bug 576970 have progressed enough that we need to make a cut and move any further changes to a follow-up--this bug. For starters: - Bug 602715 - Sync UI: Only mention enabled engines in client wipe confirmation dialog - Bug 612699 - Sync UI: Update to simplify crypto Unlike with bug 576970, where I added only bugs as dependencies that I had already ported, any FF4 Sync UI changes that landed after the set included in bug 576970 should be added as dependencies here.
Removing bug 612584 from depends list since we'll be saving as xhtml from the start.
No longer depends on: 612584
Removing bug 619995 from depends list since it's now fixed in the setup dialog patch over at bug 618709.
Adding bug 526445, though we might not want all changes (but e.g. the richlistbox might help with larger lists of engines).
When porting bug 626949 we need to take care not to run into bug 629305. BTW I think this meta bug should not block anything. Individual porting bugs (which need to be filed as required) should block instead. This bug should just serve as a tracker for full FF4 fix compatibility, whether we achieve it for 2.1 or not.
Removing bug 595725 from the list since I already covered the popup check in initUI from the start and the other part is unnecessary since it's inside alltabsPopupShowing which is only ever called from the initUI code which adds an event listener to the very same popup.
Component: UI Design → Sync UI
QA Contact: ui-design → sync-ui
Blocking final on this as really a tracking bug.
blocking-seamonkey2.1: ? → final+
All dependancies are fixed, this is not assigned to anyone, and no explanation for the final+ to ? change. If this needs to block b3 you have around 24 hours to say why, and push for it.
blocking-seamonkey2.1: ? → -
(In reply to comment #7) > All dependancies are fixed Well sure, these are mostly Firefox bugs which have not been ported yet. ;-) > this is not assigned to anyone Makes no difference since it's a meta and anything related to Sync gets done solely by me anyway. > and no explanation for the final+ to ? change. I was probably acting on an old version of the page (before IanN set final+). > If this needs to block b3 you have around 24 hours to say why, and push for it. No need to block b3, and no sense to block on a meta bug at all. All is fine.
Jens, is this worth dropping from relnotes? (RESOLVING since its a meta bug that no longer has any deps)
Status: NEW → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → FIXED
Callek, comments 0 and 8 clearly state that the dependencies of this bug (except bug 576970) are all FF bugs. It would be cleaner if someone took the time to file SM bugs for all those of course, but I currently lack the time to go through all of those.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
(In reply to Jens Hatlak (:InvisibleSmiley) from comment #10) > Callek, comments 0 and 8 clearly state that the dependencies of this bug > (except bug 576970) are all FF bugs. O whops, read too fast; sorry.
You need to log in before you can comment on or make changes to this bug.