Chromium Blog

Making Chrome more accessible with extensions

Wednesday, June 30, 2010

work hardsome extensionsgalleryAccessibility implementation guideDeveloper's Guideopen sourcedChromeVis

extensionSummer of Code projectGoogle Moderator topicPosted by Rachel Shearer, Software Engineer

Enabling Adobe Flash Player support in Google Chrome’s stable channel

Wednesday, June 30, 2010

announcednext generation browser plug-in APIsecurity risksandboxPosted by Jeff Chang, Product Manager

Improving plug-in security

Monday, June 28, 2010

browsers including Firefox and Chromeremarkable swingsuch as plug-ins

More powerful plug-in controls: Google Chrome now has the ability to disable individual plug-ins (about:plugins) or to operate in a “domain whitelist” mode whereby only trusted domains are permitted to load plug-ins (Options->Content Settings->Plug-ins).

Autoupdate for Adobe Flash Player: By including Adobe Flash Player -- the most popular plug-in -- with Google Chrome, we can re-use Google Chrome’s powerful autoupdate strategy and minimize the window of risk for patched vulnerabilities.

Integrated, sandboxed PDF viewing: We have announced an integrated PDF viewer plug-in running inside Google Chrome’s sandbox. This will make it harder for PDF-based vulnerabilities to result in the persistent installation of malware.
Protection from out-of-date plug-ins: Medium-term, Google Chrome will start refusing to run certain out-of-date plug-ins (and help the user update).
Warning before running infrequently used plug-ins: Some plug-ins are widely installed but typically not required for today’s Internet experience. For most users, any attempt to instantiate such a plug-in is suspicious and Google Chrome will warn on this condition.
A next generation plug-in API: “Pepper” makes it easier to sandbox plug-ins.

User safety is of paramount importance to us, including threats to our users caused by plug-ins outside of our direct control. We are working hard to improve the security of the entire browser ecosystem for Google Chrome users.
Posted by Chris Evans, Julien Tinnes, Michal Zalewski; Google Security Team

A fresh coat of chrome

Friday, June 25, 2010

Omniboxdev channel

When you are typing into the Omnibox, an icon to the left will show how your input will be interpreted - such as a magnifying glass for search queries (

), and a globe for URLs (

). When you’re not typing, the same icon can be dragged to another document to copy the current page’s URL, or clicked to reveal information about the current site.

When on a secure (SSL) site, this icon changes to a lock (

) - previously we displayed the lock icon at the end of the Omnibox, but now it’s closer to the URL and in a more obvious place.

We’ve added a clearer presentation of Extended Validation (EV) certificate holder names (

), which, like the lock, are now at the beginning of the Omnibox.

We’ve changed the colors and icons used with secure sites to make mixed content more obvious, and avoid confusion about ambiguous colors.

In some situations, we’ve stopped displaying “http://” and/or a slash after the hostname. This makes the hostname more prominent and the URL more readable, and provides more visual distinction between regular and SSL websites (which keep their “http://” prefix). We’ve also done a lot of work to make sure that copying and pasting of these URLs continue to work as you would expect.

The bookmark star icon (

) has joined the other “page actions” at the right-hand side of the Omnibox.

Stop and Reload have been combined, and Go eliminated, to make things simpler and keep all the navigation-related toolbar buttons together.

Posted by Nicholas Jitkoff, User Experience Designer

Extensions in Incognito

Thursday, June 24, 2010

Mouse StrokePasswordMaker

Note to extension developers: incognitochrome.extension.inIncognitoTabSaving data and incognito modePosted by Matt Perry, Software Engineer

HTML5 Rocks!: A resource for open web developers

Tuesday, June 22, 2010

HTML5 Rocks

nine tutorialstake your application offlineaccess the user's location with Geolocationread local files from within JavaScriptInteractive PresentationCreative Commons Attributioncode playgroundhandpicked resources@ChromiumDevChromium HTML5 group
Posted by Paul Irish, Google Chrome Developer Relations

Bringing improved PDF support to Google Chrome

Thursday, June 17, 2010

As we’ve previously mentionednext generation browser plug-in APIour effortsmaking available

PDF files will render as seamlessly as HTML web pages, and basic interactions will be no different than the same interactions with web pages (for example, zooming and searching will work as users expect). PDF rendering quality is still a work in progress, and we will improve it substantially before releasing it to the beta and stable channels.

To further protect users, PDF functionality will be contained within the security “sandbox” Chrome uses for web page rendering.

Users will automatically receive the latest version of Chrome’s PDF support; they won’t have to worry about manually updating any plug-ins or programs.

next generation browser plug-in APIPosted by Marc Pawliger, Engineering Director

Google Chrome Frame - Now in Beta

Tuesday, June 8, 2010

Google Chrome Frameinitial launchGoogle Chrome 5.0MeeboWordPressgive Google Chrome Frame a trydev channeldocumentationfeedbackfiling bugs
Posted by Amit Joshi, Software Engineer, and Alex Russell, Software Engineer

Google Chrome Developer Update - Google I/O recap, new APIs

Monday, June 7, 2010

Google I/O recap
If you missed the Day 1 keynote this year, it was all about the open web. There were some amazing demos from Mugtug, TweetDeck, Adobe, and Sports Illustrated demonstrating the full potential of HTML5. There was a preview of WebM/VP8, a high-quality, open, and web-optimized video format. We saw the announcement of the Chrome Web Store, which later this year will provide a new and exciting channel for developers to distribute their web apps and reach new users. We also launched the Google Font API, which allows you to add high-quality web fonts to any web page. Lastly, there were all of the great Chrome sessions. Videos have been posted on the Google I/O website:

What's new for developers in Google Chrome?
The Google Chrome Dev channel is now up to 6.0.422.0. It includes a bunch of new features to think about when developing your apps:

In addition to the above, there are new experimental extension APIs:

You can try out these features by launching a Dev-channel version of Google Chrome with the --enable-experimental-extension-apis flag and adding the ‘experimental’ permission in your manifest.json file. Please keep in mind that these features are still under development and are not 100% stable yet.
Upcoming developer events
For those of you based in New York, there’s an upcoming Chrome Extensions hackathon in our local office on June 10, 2010. We also have a five day DevFest starting June 28, 2010 in Sydney, Australia. Google Chrome will be featured on Wednesday, June 30. Stay tuned for more details!
For the latest news and upcoming developer events, subscribe to this blog and follow us on Twitter @ChromiumDev.
Posted by Eric Bidelman, Google Chrome Developer Relations

An update on Google Cloud Print

Monday, June 7, 2010

announcedannounced

Watch live streaming video from hpkickoff at livestream.comdocumentationPosted by Mike Jazayeri, Group Product Manager

Google Chrome’s Developer Tools Improve Productivity

Friday, June 4, 2010

At Google I/O 2010 we presented on Google Chrome’s Developer Tools and enjoyed getting the in-person feedback from developers. We wanted to list some of the new and improved features we presented at I/O that set apart our tools in helping developers become more productive.

The Scripts panel now allows editing JavaScript without having to reload the page. Just double-click on the line in the function body while debugging and make your changes. We’ll patch the underlying optimized machine code at run-time and continue the execution. [video]
CPU profiler captures the state of your app at a rate of 1,000 samples per second without modifications to the running optimized machine code. The resulting tree view makes it easy to find out where to focus efforts on speeding up the web app. [video]
The new Timeline panel provides a simple view of the AJAX application execution. It records everything that happens in the browser from JavaScript execution to styles re-calculations and then visualizes it in a simple waterfall with timing information and traces to the source code. See the demo fragment at [video].
The improved Heap profiler can take snapshots of the JavaScript heap, visualize and compare them. This makes finding and fighting memory leaks a much easier task. See the demo fragment at [video].

We also covered a number of general Inspector improvements in the WebKit blog recently. Watch them live in the DevTools panel walk through from the I/O video.

We welcome feedback: to submit a bug or feature request please use the Chromium issue tracker and mention DevTools in the summary.
We hope you like the new improved Google Chrome Developer Tools. Note that some of the features above are only available on Google Chrome’s Dev Channel at this moment. For more info please check out the DevTools site.
Posted by Pavel Feldman, Software Engineer

WebSocket Protocol Updated

Wednesday, June 2, 2010

WebSocket is "TCP for the Web," a next-generation full-duplex communication technology for web applications being standardized as a part of Web Applications 1.0. The WebSocket protocol is more efficient than HTTP as used in Ajax, so it is more suitable for real time and dynamic web applications. WebSocket also provides a very simple API that can be used to communicate bidirectionally between the web browser and a server, so it makes it easy to develop such web apps.
We initially implemented WebSocket in WebKit, which has been available in WebKit nightly builds and in Google Chrome. The initial implementation was based on draft-hixie-thewebsocketprotocol-75. Early adopters were able to start developing web apps using WebSocket on real browsers, and provide feedback about the WebSocket specification.
Based on community feedback, the WebSocket specification has been updated to draft-ietf-hybi-thewebsocketprotocol-00 (also known as draft-hixie-thewebsocketprotocol-76).This version relaxes requirements on handshake messages to make it easier to implement with HTTP libraries, and introduces nonce-based challenge-response to protect from cross protocol attacks. These changes make it incompatible with draft-hixie-thewebsocketprotocol-75; a client implementation of -75 can’t talk with a server implementation of -76, and vice versa.
Developers should be aware that starting from WebKit nightly build r59903 and Chrome 6.0.414.0 (r47952), the client will talk to a server using -76 version of the protocol, so it will fail to open WebSocket connections with a WebSocket server based on draft-hixie-thewebsocketprotocol-75. Since -75 version of the protocol is obsoleted and no longer supported in future version of browsers, to support new clients you need to update the server implementation. (Note that Chrome 5 uses -75 version of protocol).
The WebSocket protocol is still actively being changed. Until there is more consensus, we will continue to update our implementation to follow the latest draft of specification, rather than worrying about breaking changes.
We’re more than happy to hear your feedback, and encourage you to file any bugs you find on our issue tracker.
Posted by Fumitoshi Ukai (鵜飼文敏), Software Engineer

In The Open, For RLZ

Wednesday, June 2, 2010

When we released a new stable version of Google Chrome last March, we tried to improve the transparency and privacy options of Google Chrome. One area where we’ve seen a lot of interest and questions is the RLZ library that is built into Google Chrome. RLZ gives us the ability to accurately measure the success of marketing promotions and distribution partnerships in order to meet our contractual and financial obligations. It assigns non-unique, non-personally identifiable promotion tracking labels to client products; these labels sometimes appear in Google search queries in Google Chrome.
Documenting Google Chrome’s use of promotional tags and tokens was a good start, but we wanted to take this transparency a step further. Our goal was to not only show you exactly how we were sending distribution information, but also what information was included and how it was generated.
Today, we’ve open-sourced the code that generates the RLZ parameter that sometimes appears in Google search queries. We’ve made the RLZ library its own project on the Google Code site, since this is the same library that is used in other Google products. This is analogous to how we opened Omaha, the Google Updater technology, as its own open-source project.
Chromium will also continue to exist as it always has, without any RLZ library included. And, you can still download a Google Chrome with no RLZ behavior at www.google.com/chrome. But now that RLZ is open, Google Chrome distributed through promotional means will include this open-source implementation of RLZ.
It is our hope that we are not only opening up a previously-closed part of Google Chrome and providing better transparency, but that we’re also offering up potentially useful code to others who may use it in their own projects.
We know this is just a small step, but we think that the RLZ project will provide better transparency and value to the community. We want to hear what you think, so please keep the feedback coming!
Posted by Roger Tawa, Software Engineer, and Glenn Wilson, Product Manager

什么是帽子戏法	炎性肉芽肿是什么意思	为什么会长腋毛	什么叫道德绑架	死海为什么叫死海
总胆红素偏高是什么引起的	固执己见是什么意思	女人吃牛蛙有什么好处	空巢老人什么意思	梦见水是什么征兆
高锰酸钾用什么能洗掉	斯沃琪手表什么档次	三五成群是什么意思	南瓜与什么食物相克	疱疹吃什么药可以根治
双肾尿酸盐结晶是什么意思	满月送什么礼物好	北京大裤衩建筑叫什么	本科属于什么学位	登革热是什么症状

抑郁到什么程度要吃氟西汀mmeoe.com	维生素C起什么作用hcv9jop3ns8r.cn	术后吃什么水果hcv8jop6ns3r.cn	丞相和宰相有什么区别hcv8jop2ns1r.cn	眼睛为什么会近视hcv7jop7ns1r.cn
女性私处长痘痘是什么原因hcv8jop4ns8r.cn	虎头蛇尾是什么意思hcv9jop3ns0r.cn	寒湿体质吃什么中成药weuuu.com	血白细胞高是什么原因hcv7jop9ns2r.cn	当今社会什么行业前途比较好hcv7jop5ns4r.cn
大豆是什么豆hcv9jop6ns8r.cn	山水有相逢是什么意思hcv8jop3ns6r.cn	细菌性阴道炎吃什么药aiwuzhiyu.com	学业是什么意思hcv8jop5ns0r.cn	一个万一个足念什么wuhaiwuya.com
万宝龙皮带算什么档次hcv8jop5ns5r.cn	scr医学上是什么意思hcv8jop4ns9r.cn	赛能是什么药hcv7jop7ns2r.cn	尿多是什么问题hcv8jop2ns1r.cn	身心疲惫是什么意思hcv8jop9ns6r.cn

Chromium Blog

Making Chrome more accessible with extensions

Enabling Adobe Flash Player support in Google Chrome’s stable channel

Improving plug-in security

A fresh coat of chrome

Extensions in Incognito

HTML5 Rocks!: A resource for open web developers

Bringing improved PDF support to Google Chrome

Google Chrome Frame - Now in Beta

Google Chrome Developer Update - Google I/O recap, new APIs

An update on Google Cloud Print

Google Chrome’s Developer Tools Improve Productivity

WebSocket Protocol Updated

In The Open, For RLZ

Labels

Archive

Feed