Burning Question of the Day: Why does Firefox convert the unicode, ascii, hex codes for special characters to human-readable text when you view source? What if I want to know which one the site is using?
This is just one of those burning questions and not something I’m having problems with. I currently use the web-developer tools to look at code from other people’s websites… so, no this Firefox “feature” does not hinder my work. :)
This is just one of those things that will make me tickle inside for a while. Like, whose call was it to make Firefox’s “view source” function auto-render the special characters and leave out the cute little codes? Did people complain?
To me, anyone who’s interested in the source of a page is going to be interested in all of the code… not just the html.
Heh.
Chris | 01-Aug-06 at 1:45 am | Permalink
Maybe it is some kind of defensive design. Or another symptom of the mac-ification of the world.
Yuvi | 02-Aug-06 at 12:11 am | Permalink
Hi,I would like to know more about the linux, in SEO, any idea, get in touch with me @ yuva_raju_raj@yahoo.co.in
peridyd | 04-Aug-06 at 12:01 pm | Permalink
Emily,
Imagine what it would look like if the target language were Japanese, Korean or some other language that’s really leveraging Unicode. If the source code weren’t rendered, it could be utterly unreadable. What I’d rather see is the ability to toggle it.
You ought to file it as a bug/feature on the Firefox site. Then again, maybe it already is.
Dennis
dolphinling | 15-Aug-06 at 7:32 pm | Permalink
It doesn’t, unless you use View Selection Source. When you use view selection source, it gives you a (part of a) re-serialized DOM, because with badly-malformed html, it might be impossible to give you the actual source.