chrishtr

Many browsers now have AI agents built into them. For example, Chrome has Gemini-in-Chrome, and Atlas has ChatGPT. When a user is on a website and then opens the built-in browser AI agent, the AI agent will see the WebMCP tool calls for that website and be able to call them.

It's not government owned and operated. It's just on government land.

The issues were fixed actually.

https://github.com/whatwg/html/wiki/dialog--initial-focus,-a...

https://github.com/whatwg/html/pull/8199

The <dialog> element is fully styleable, including its backdrop (the MDN article explains how for the latter). In Chrome you can also fully style animations opening and closing a <dialog> or popover.

https://developer.chrome.com/blog/entry-exit-animations

Implementation already begun for Firefox:

https://groups.google.com/a/mozilla.org/g/dev-platform/c/4cb...

Thanks! Glad you enjoyed it.

Author here. I'm curious - what did you think of the chapter?

Author here.

That article, along with a number of other resources, are listed here:

https://browser.engineering/bibliography.html

In my view, a critical part of really learning how something as complicated as a browser works is by trying to build it yourself. That's why our book is oriented around building a browser as you go.

Author here.

I'm the rendering lead for Chrome, and know quite a lot about how it works. I also recently wrote a series of articles about the new rendering architecture of Chromium, see here:

https://developer.chrome.com/blog/renderingng/

Pavel is a professor at the University of Utah and has extensively studied CSS from an academic point of view. He also has a lot of experience teaching the material and making it accessible to students.

Author here.

That's exactly what we are hoping for.

http://browser.engineering/preface.html

So far, my co-author Pavel has taught from this book multiple times (including this semester). In the spring at least one other university will offer a course. We'll list all known courses offerings on the website.

Also, if anyone would like to teach from this book, please get in touch!

(blog post author here)

Could you file a bug with an example at crbug.com/new?

"should not affect WebGL" is probably a better way to put it. (No software has no bugs or unintended consequences...)

(I'm the author of this blog post)

The launch in Chrome 94 does not affect WebGL. It's just for HTML/CSS content.

If you can reproduce the issue and can share a URL that does so, please file a bug at crbug.com/new for us to investigate.

(I'm the author of this blog post and lead for a large area of the work described): thanks!

See https://developer.chrome.com/blog/renderingng/ for some idea of the scale of investment being made.