Browser displays font sizes incorrectly at Bloglines.com, when connected through ssh-tunnel and Squid 2.5 proxy server.

VERIFIED WORKSFORME

Status

()

Core
Layout: Text
VERIFIED WORKSFORME
13 years ago
9 years ago

People

(Reporter: Matti J. Kärki, Unassigned)

Tracking

({qawanted})

Trunk
x86
Windows XP
qawanted
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(URL)

Attachments

(3 attachments)

(Reporter)

Description

13 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.7.3) Gecko/20040913 Firefox/0.10
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.7.3) Gecko/20040913 Firefox/0.10

When connected through an SSH tunnel to a Squid web proxy server and the
personal Bloglines.com page is loaded, the font sizes at the left and the right
frame are incorrect. When connected directly to Internet, there is no problems
with font sizes.

Reproducible: Always
Steps to Reproduce:
1. Create an SSH tunnel to a machine running Squid web proxy server.
2. Tell the browser to use the SSH tunnel as a HTTP proxy.
3. Load http://www.bloglines/myblogs/ page (you have to have a user account at
Bloglines.com).

Actual Results:  
The Bloglines page is divided to two frames. Usually at the left frame, the font
sizes are correct. At the right frame, the font sizes are too large. Normally
few reloads are enough to fix the fonts. Using Ctrl-+ / Ctrl-0 doesn't help.

Expected Results:  
When page is loaded correctly, fonts are in equal sizes at the both frames at
the web page.
(Reporter)

Comment 1

13 years ago
Created attachment 159085 [details]
This screenshot shows how the font size is too large at the right frame.
(Reporter)

Updated

13 years ago
Summary: Browser displays font sizes incorrectly at Bloglines.com, when connected through ssh-tunnel and swuid 2.5 proxy server. → Browser displays font sizes incorrectly at Bloglines.com, when connected through ssh-tunnel and Squid 2.5 proxy server.
Is the browser getting the same data in both cases?
(Reporter)

Comment 3

13 years ago
(In reply to comment #2)
> Is the browser getting the same data in both cases?

Yes. I compared the HTML source received via proxy and via direct connection and
there is no differences between source codes. I also checked the Style Sheets
and it seems that there is no additional Style Sheet files transferred from the
host. All style information is embedded into the HTML source. So there should
not be any problems with tranferring CSS files.

I should also point out that the bug #217527 behaves really badly with this kind
of proxy settings. So, could it be some sort of timing issue or something (just
quessing here)?
Possible.  Could you test a current trunk build (which would have the fix to bug
217527 and whatever else has been fixed in the last 6 months), please?
(Reporter)

Comment 5

13 years ago
(In reply to comment #4)
> Possible.  Could you test a current trunk build (which would have the fix to bug
> 217527 and whatever else has been fixed in the last 6 months), please?

I tested with "Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a4)
Gecko/20040920 Firefox/0.9.1+" which claimed to be a nightly trunk build
2004-09-20. Same problem. I'll attach couple screenshots showing the feature.
(Reporter)

Comment 6

13 years ago
Created attachment 159599 [details]
Nightly build 2004-09-20 showing unacceptable font behaviour.
(Reporter)

Comment 7

13 years ago
Created attachment 159600 [details]
This is how things should look like (compare to the image above, 2004-09-20).
Keywords: qawanted
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
Reporter ( Matti J. Kärki) : Is this still an issue with recent builds ?
(Reporter)

Comment 10

9 years ago
No, this is not an issue any more. The Firefox has been working flawlessly with Bloglines and different proxies (including the exact same ssh+squid setup, which was used when this bug report was originally created).
Thanks for retesting!
Status: UNCONFIRMED → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → WORKSFORME
and thanks for the answer after 5 years, most people are gone after that time (but BZ is still there ) !
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.