Closed Bug 452327 Opened 11 years ago Closed 6 years ago
Create XUL app or extension to mirror major update window
In testing the major update window, we had to check a number of locales on a number of OSes/platforms to see if the content fit inside the window just perfect. Pascal created a webpage to do most of this, but we found further problems when testing on the actual website using real builds. We should have an extension or XUL app that is simply the major update window with a one-button push for showing or hiding the extension out of date issue. I envision: ------------------------------------------- | _____ | | Enter locale: |_____| | | __ __ | | (__Show Notice__) | | | | _____________________________________ | | | | | | | | | | | Update window | | | | | | | |_____________________________________| | |___________________________________________| Since we're going to be testing this for every new major update, it'd be nice to have a way to really test it. Is this doable?
Oh, and it in case it wasn't clear, this should probably pull from trunk or just have a user-changeable URL where it could pull from to test.
Can you go over some of the issues you ran into besides the need to test each of the locales? For example, what changes had to be made (if any) for any of the locales or what changes had to be made at all from the results found during the testing? Perhaps we could force a minimum width in px on this ui and make the details and license contents a fixed size that works with that minimum width and center it? This would allow the locales to specify a width that would allow increasing the width.
(In reply to comment #2) > Can you go over some of the issues you ran into besides the need to test each > of the locales? For example, what changes had to be made (if any) for any of > the locales or what changes had to be made at all from the results found during > the testing? The design that was made (which changes for each release so far) is designed specifically for that window. Once we change any text (like, for each locale), it causes a horizontal scrollbar in the UI. Additionally, some of CSS caused a vertical scrollbar when the content clearly fit visually, but was maybe two pixels off technically. > Perhaps we could force a minimum width in px on this ui and make the details > and license contents a fixed size that works with that minimum width and center > it? This would allow the locales to specify a width that would allow increasing > the width. > From my understanding, I think the locales can already specify a width for their window in ems. I'm not sure about that though. Pascal?
(In reply to comment #3) >... > From my understanding, I think the locales can already specify a width for > their window in ems. I'm not sure about that though. Pascal? They can
I was referring to enforcing a minimum size to prevent scrollbars. So, each locale has its own details page served up or is the content the same for all of them?
Each locale has it's on localized details page but the content is the same. The localizers can specify a specific width in em to the whole dialog, but have no control on the frame inside this window that displays the external web page. The size of this frame is not fixed and depends on several factors like the default font size, the width of the dialog for the platform (we have a specific setting for Mac) and some other constraints.
a couple of notes: iirc the height and width of a wizard is not sized differently on a per locale basis on Windows. the current wizard on windows is not the standard size on windows.
Here's the extension.
Deprecating Testing :: Infrastructure, and this sounds like it was completed.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.