Closed
Bug 269665
Opened 20 years ago
Closed 20 years ago
Wrong font used in ViewSource
Categories
(Core Graveyard :: View Source, defect)
Core Graveyard
View Source
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: e7online, Assigned: mrbkap)
References
()
Details
Attachments
(3 files)
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8a5) Gecko/20041024 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8a5) Gecko/20041024 Tested in: - Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8a5) Gecko/20041024 - Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8a5) Gecko/20041024 If the charset of a page is "shift_jis" the source window, the font of the source code looks bigger than normal. If I see the website this is correct, but if I view the source there should be none changes on the font size depending on the web page. An other charset will be ok but the font size is my own decision. Reproducible: Always Steps to Reproduce: 1. Load Page http://www.shrinkwrapvb.com/avihelp/avihlp_5.htm or the page you'll see bottom 2. Choose View, Page Source 3. See ;) -------------------------------------- Sample code: <html><head> <meta http-equiv="Content-Type" content="text/html; charset=shift_jis"> </head><body> Test page </body></html> Actual Results: To big font in SourceView Expected Results: The normal font size in which is displayed all other source code of all other pages
This is a simple screenshot showing the bug/missing feature [edited]
Comment 2•20 years ago
|
||
I´m seeing this too on Big-5 sites. But maybe it is deliberate, are people using shift_jis or BIG-5 are used to greater line-heights? related: Bug 89549 Set View Source font family and size workaround: You can style the viewsource content using userContent.css see bug 89549 comment 10
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment 3•20 years ago
|
||
What is jp2? Let's stick to traditional formats for screenshots please.
Comment 4•20 years ago
|
||
Reporter, are you font size settings for Japanese and Western encodings the same (check your preferences)?
Comment 5•20 years ago
|
||
seen with view-source:http://www.shrinkwrapvb.com/avihelp/avihlp_5.htm I don´t have japanese fonts installed, so I got a pop-up from mozilla for downloading fonts, I denied. This font seems to be about 20% higher then the western font, see next attachment
Comment 6•20 years ago
|
||
Comment 7•20 years ago
|
||
wfm Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.8a5) Gecko/20041118 I don´t have Japanese fonts installed, but I do have settings, for monospace differing from western. Western, Arabic, others Proportional, Serif, 16 pixels Monospace, Courier New, 13 pixels Japanese, Chinese, Korean Proportional, Serif, 16 pixels Monospace, , 16 pixels Seems to me that 13 pixel is the default size for one group of languages, and 16 pixels the default for another one. There are also more fonts specified for the first group. After changing size of Monospace for Japanese to 13 pixels I get the same size.
Comment 8•20 years ago
|
||
Yes, the monospace font size for East Asian languages defaults to a larger value because those fonts are typically not readable at the smaller font size we use for Western languages. Hence the question in comment 4.
Comment 9•20 years ago
|
||
(In reply to comment #8) > Yes, the monospace font size for East Asian languages defaults to a larger value > because those fonts are typically not readable at the smaller font size we use > for Western languages. > > Hence the question in comment 4. That´s been the answer to my question in comment 2, so I assume this bug could be resolved as wfm, or does it make sense, and is easy to implement, to show html tags and eastern content in different font sizes for the monospace font used in in view-source: ?
Comment 10•20 years ago
|
||
> or does it make sense, and is easy to implement
It doesn't make much sense and hence is hard to implement (layout assumes you'll
want to do the sensical thing here),
Marking invalid, but reporter, please reopen if the font size is set the same
and you still see the problem...Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → INVALID
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•