Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Nonsense characters appear in Android Froyo web browser #129

Closed
rspeer opened this issue Aug 31, 2011 · 4 comments
Closed

Nonsense characters appear in Android Froyo web browser #129

rspeer opened this issue Aug 31, 2011 · 4 comments

Comments

@rspeer
Copy link

rspeer commented Aug 31, 2011

I have confirmed with two different phones that if you visit a very simple Bootstrap site with the stock Android Froyo web browser, a box (of the kind that tends to represent "invalid character") appears whenever the source HTML has a line break in a paragraph.

I'm not talking about an HTML line break like <br>, I mean that when you put a line break in the .html file, it shows up as a box instead of a space on the web page.

This occurs on the Bootstrap-using web page at http://lumino.so. A minimal case that reproduces it is at http://lumino.so/bug.html.

@fat
Copy link
Member

fat commented Aug 31, 2011

sorry, we don't currently support that browser

@fat fat closed this as completed Aug 31, 2011
@alexgibson
Copy link

This single CSS rule might be your culprit: text-rendering: optimizelegibility;

Can I suggest you re-open this issue, as there might be a very straight forward fix given a quick search in the Android bug tracker?

http://code.google.com/p/android/issues/detail?id=15067

I'd suggest either not applying it to the body (both for the above reason and for performance reasons), and applying it only to headings.

Looks like this issue effects android 2.1 through to 2.3. Seems a bit silly to have every site created with bootstrap to look weird on the vast majority of Android phones, when it might actually be down to just a single CSS property?

@rspeer
Copy link
Author

rspeer commented Sep 1, 2011

I don't think it should apply to headings either. That's just asking for a nasty surprise. In fact, I first noticed it in a heading that happened to span two lines of HTML source.

My mind is also boggled by fat's instant closing of this bug. Actively breaking on the current version of a popular browser is a bug in any web project, no matter which browsers it has decided to officially target. To assert otherwise sounds like those short-sighted banners from the '90s saying "This site is only viewable in Netscape 3.0".

@fat
Copy link
Member

fat commented Sep 1, 2011

There's an open pull request for removing that property, so we're not going to reopen this issue. Thanks though!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants