Skip to main content

Is Chrome intentionally trying to mess up web development?

A couple of weeks ago I posted about the weird behavior of Chrome's omnibox. Today, am posting about how Chrome's bungled a very simple feature of all web browsers. Since the very early days of the web, web browsers have always had an option for viewing the source code of the currently rendered page. Typically the menu is called "View Source" or something similar. You click it and you get the HTML source for the page you're looking at. Very simple, right? Well Chrome does it differently. In the spirit of complicating simple things, clicking on "View Source" in Chrome doesn't just give you the HTML of the current page. Oh no! It makes another request to the web server and shows you the HTML for that version. Yep. I am not sure how that's better than just showing the HTML of the already rendered page but that's what Chrome does. So in addition to using the omnibox to complicate web development, the "View Source" option makes a trivial action more complicated. BTW, who uses that option the most? Developers. The very same people who invoke that option because something in the currently rendered page is incorrect. And God help you if you have a debugger attached to the webserver process (as developers typically do).

Why am I so sure that Google messed this up? First, all the problems associated with their implementation of the omnibox that I described in my previous post apply here also. Second, Google "view source chrome" and you'll get a bunch of results describing this odd behavior. If that many people are having problems with this simple command, perhaps they ought to fix it?

Comments

Popular posts from this blog

Career 101: Dunk, layup or dribble out of bounds?

Saw this on Whisper:


The way I see it, this dude has 3 options:
Reject the $55K increase and stick with his old job that he loves (dribble out of bounds)Take the $170K to his current boss and negotiate for a raise (layup)Take the $170K job, stick with it for a year and then bounce (dunk) The first option is what I call a poor person's advice. It sounds very noble...very "get a job you love and you'll never work". Well I am here to say that's bullshit (mostly). This is business; you should always get the most you can. Besides, this is a chance for this dude to change his baseline salary for future jobs. At his current job, getting that $55K will take several years because corporate America isn't going to offer you more than a token raise each year.

My advice would be to take the $170K offer to his current manager and get him/her to match it or raise his current salary. That's the layup option. It's not too money-hungry and doesn't summarily leave $5…

Strong, Likely Boy

Item # 19:

Infant. Age 1. Described as "Strong, Likely Boy" $400.00





What to do?

I recently bought one of those wireless earbuds from Amazon. I spent some time researching all the available options and finally picked this particular one. It was highly rated on Amazon 5 stars from 54 reviewers (most of them "verified purchase"). Not great but not bad. Anyway, the earbuds arrived and I found this in the box:

Hmm, OK. Very mysterious. As instructed, I sent them an email for further information. Here's what I received:

Funny thing is I really like the ear buds. Excellent build quality and thus far, great performance. They reconnect to my phone 2-3 seconds after taking them out of the case. It's easy to create a good seal...sometimes so good I get that underwater feeling one gets with noise cancelling headphones. Even without the 40% incentive, I would have written a review...that's how much I like the ear buds. But now I feel weird about doing it. I wonder how many of those 54 5-star reviews were motivated by a 40% discount.

As for the 40% discou…