How a bug report on my blog turned out to be a WebKit engine issue
I was minding my own business when someone reported a bug on my site 1.
Nothing unusual, right? Not quite! When I tested I thought it was a problem related to Chroma 2, the program responsible for rendering code blocks on this site.
However, I was wrong! After some testing, the folks in the Chroma community found it to be a WebKit engine problem. More specifically, the browser doesn’t respect the specified text size when content exceeds a certain length 3. The code blocks were rendering with incorrect font sizes, making them harder to read and unpleasing.
The bug happens when iPhone users visit my site using Safari. The reason is that WebKit has a feature that auto-corrects font sizes, and this auto-correction makes code blocks look weird with some lines bigger than others.
Therefore, I have two options: add the suggested fix on my end (a CSS rule that disables text auto-sizing) or wait until they fix it in the web engine.
Cool, isn’t it?