Closed
Bug 346546
Opened 18 years ago
Closed 18 years ago
Clean up unknownContentType.xul
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
FIXED
Firefox 2
People
(Reporter: beltzner, Assigned: mwu)
Details
(Keywords: fixed1.8.1)
Attachments
(1 file)
|
1.21 KB,
patch
|
mconnor
:
review+
mtschrep
:
approval1.8.1+
|
Details | Diff | Splinter Review |
The dialog currently looks like:
You have chosen to open
## AutoHotkey104408_Install.exe
which is a: Application
from: http://www.autohotkey.com
Would you like to save this file?
( Save File ) ( Cancel )
There should be an extra CR/LF between the summary and the question to the user:
You have chosen to open
## AutoHotkey104408_Install.exe
which is a: Application
from: http://www.autohotkey.com
Would you like to save this file?
( Save File ) ( Cancel )| Reporter | ||
Comment 1•18 years ago
|
||
Mike, this didn't show up in your screencaps from when you added some indentation to the text in this dialog in bug 344984. Could I get you to add the extra CRLF? Should be a pretty simple fix ...
Comment 2•18 years ago
|
||
I don't even see that text in a current trunk build - seems like the patch for bug 315536 introduced duplicate elements with the same ID (<description id="source"> and <label id="from">). This seems broken.
| Assignee | ||
Comment 3•18 years ago
|
||
(In reply to comment #1) > Mike, this didn't show up in your screencaps from when you added some > indentation to the text in this dialog in bug 344984. Could I get you to add > the extra CRLF? Should be a pretty simple fix ... > If you look at the linux screenshots, it is there. That was the first thing I did when I opened bug 344984. But Windows doesn't show "Would you like to save this file" at all, most likely for the reason Gavin gave in comment #2.
Assignee: nobody → michael.wu
Keywords: regression
Summary: unknown content type dialog needs CRLF before &unknownPromptText.label → &unknownPromptText.label not visible on windows
| Assignee | ||
Comment 4•18 years ago
|
||
Sorry for changing this bug again, but it looks like the line not being visible was fixed by bug 315536.
Severity: normal → trivial
Keywords: polish,
regression
Summary: &unknownPromptText.label not visible on windows → Cleanup nsUnknownContentType.xul
| Assignee | ||
Comment 5•18 years ago
|
||
Attachment #231505 -
Flags: review?(mconnor)
| Assignee | ||
Comment 6•18 years ago
|
||
(In reply to comment #5) > Created an attachment (id=231505) [edit] > Clean up unknownContentType.xul > We could probably get rid of the surrounding hbox, actually..
Updated•18 years ago
|
Summary: Cleanup nsUnknownContentType.xul → Clean up nsUnknownContentType.xul
Comment 7•18 years ago
|
||
Comment on attachment 231505 [details] [diff] [review] Clean up unknownContentType.xul r=me, sorry about the delay
Attachment #231505 -
Flags: review?(mconnor) → review+
| Assignee | ||
Comment 8•18 years ago
|
||
Checking in toolkit/mozapps/downloads/content/unknownContentType.xul; /cvsroot/mozilla/toolkit/mozapps/downloads/content/unknownContentType.xul,v <-- unknownContentType.xul new revision: 1.16; previous revision: 1.15 done
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
Target Milestone: Firefox 2 beta2 → Firefox 2
| Assignee | ||
Comment 9•18 years ago
|
||
Comment on attachment 231505 [details] [diff] [review] Clean up unknownContentType.xul Low risk, and eliminates multiple elements with the same ID.
Attachment #231505 -
Flags: approval1.8.1?
Comment 10•18 years ago
|
||
Comment on attachment 231505 [details] [diff] [review] Clean up unknownContentType.xul a=schrep for drivers for low-risk 1.8 regression fix.
Attachment #231505 -
Flags: approval1.8.1? → approval1.8.1+
| Assignee | ||
Comment 11•18 years ago
|
||
Checking in toolkit/mozapps/downloads/content/unknownContentType.xul; /cvsroot/mozilla/toolkit/mozapps/downloads/content/unknownContentType.xul,v <-- unknownContentType.xul new revision: 1.11.2.4; previous revision: 1.11.2.3 done
Keywords: fixed1.8.1
Summary: Clean up nsUnknownContentType.xul → Clean up unknownContentType.xul
You need to log in
before you can comment on or make changes to this bug.
Description
•