Small changes that you make to a product can have a big impact on its perception. Google removed scroll arrows in Chrome 32 on Windows, and that change infuriated part of the web browser's userbase.
What does not seem like a big deal is a major one for users who use those scroll arrows all the time to navigate web pages. While there are many alternatives available, it is difficult to make changes if you are used to using scroll arrows for that.
The only option for affected users was to install a third-party extension for the browser that would add scroll arrows back to the browser.
This appears no longer necessary when Chrome 34 comes along, as Google has restored scroll arrows on Windows in that version.
If you are running Chrome Beta, Dev or Canary right now, then you should have scroll bars again on Windows. The next major Chrome Stable update will add those scroll arrows to the version of the browser as well.
But scroll arrows are not the only changes in Chrome 34.
If you create accounts regularly on the Internet, you may have come upon registration forms where you could not paste a password in. Or, later on, that would not allow you to paste the password in during log on, or where Chrome would not suggest to save that password for you.
The reason for this behavior is called autocomplete=off. Web designers use it to block automatic interaction with password fields. When set to off, browser's won't suggest to save passwords or fill out password forms automatically.
Google Chrome 34 ignores that so that you do not have to worry about it anymore.
On a side note: Firefox 29 comes with a preference that enables you to do the same thing. Read about it here.
Chrome 34 ships with several other features of interest. The srcset attribute enables web developers to provide a set of images for different screen resolutions and pixel densities.
The attribute essentially takes a comma-separated list of URLs each with one or more descriptors giving the maximum viewport dimensions and pixel density allowed to use the image. From the available options, the user agent then picks the most appropriate image. If the viewport dimensions or pixel density changes, the user agent can replace the image data with a new image on the fly.
To specify an image, give first a URL, then one or more descriptors of the form 100w, 100h, or 2x, where "100w" means "maximum viewport width of 100 CSS pixels", "100h" is the same but for height, and "2x" means "maximum pixel density of 2 device pixels per CSS pixel".
Web Developers may be interested in the following changes:
You can read more about the changes in Chrome 34 on the official Chromium blog.Advertisement
Ghacks is a technology news blog that was founded in 2005 by Martin Brinkmann. It has since then become one of the most popular tech news sites on the Internet with five authors and regular contributions from freelance writers.