Help Strange chrome rendering bug?

[Claghorn]

Here is a silly web page I build from a script to tell me what episodes of Doctor Who I've downloaded off my TiVo:

Downloaded Doctor Who Episodes

Does the entry for Journey's End show up in a larger font for anyone else (when looking at the page on your Nexus 7)?

Is this a chrome bug, or am I blind to something funny in the generated html?

I only see this effect on my Nexus 7, not on a desktop running chrome.

 

[John Bean]

Very obvious visually.

I can't see anything different in the html for that entry - nor can Chromium on Linux that I'm currently using - but Chrome (Android) apparently can. Odd.

 

[Claghorn]

I'm glad to know it isn't just me . I reported it via the Menu->Settings->Report Issue button. Don't know if that will have any effect though.

 

[MeatLoafT]

It looked great on mine. Nexus 7 with 4.2.2 running Chrome.

 

[Claghorn]

This just got even stranger. I started fooling around with the font-size in the style sheet and if I make the font 11pt everything renders the same apparent size, if I make it 13pt, two of the entries start showing up larger than everything else. A very strange glitch.

 

[John Bean]

Some years ago in the era of IE6 I had the misfortune of writing (and fixing existing) website code that so as to give the same rendering on IE as on other browsers. My "favourite" IE6 glitch involved the spacing of the source rather than the code itself - it broke the page layout every time anybody tried to split some long (several k long!) dense lines of html with some "harmless" whitespace to make it more human readable. Firefox (and others) didn't care - as expected - but IE6 was another matter altogether.

The Android version of Chrome doesn't appear to be related to the desktop versions in any way I can see, so I'm not surprised it has its own quirks. I think I'll call it "Rusty"

 

[Demache]

Some years ago in the era of IE6 I had the misfortune of writing (and fixing existing) website code that so as to give the same rendering on IE as on other browsers. My "favourite" IE6 glitch involved the spacing of the source rather than the code itself - it broke the page layout every time anybody tried to split some long (several k long!) dense lines of html with some "harmless" whitespace to make it more human readable. Firefox (and others) didn't care - as expected - but IE6 was another matter altogether.

The Android version of Chrome doesn't appear to be related to the desktop versions in any way I can see, so I'm not surprised it has its own quirks. I think I'll call it "Rusty"

From what I've heard, making sure everything works on as many browsers as possible is a real PITA. Especially legacy ones like IE6 and 7. Whoever has thought about keeping those around in the past 5 years ought to be shot.