4 ms·

> Firefox has added support for some webdriver APIs[1] that this proprietary "WebContainers" product depends on Hi, WebContainers does not depend on WebDriver

> Firefox has added support for some webdriver APIs[1] that this proprietary "WebContainers" product depends on Hi, WebContainers does not depend on WebDriver BiDi. We did mention our interest in this new standard getting more momentum in other blog post (which might be the source of your statement?).

dmitriid 4y ago
> We did mention our interest in this new standard getting more momentum You keep calling it a standard. The "working group" is some people on Discord. Your blog post calls it "our in-browser operating system" which is a far cry from a standard. You "team up with browser vendors directly", yet not through web standards bodies, but through some "bytecode alliance" that aims to build outside the browser. Also, unsurpisingly, zero links anywhere to an actual standards text or even to a specification of these web containers.
- jrvidal 4y ago
  > The "working group" is some people on Discord Fair enough, we should correct our mention of WebDriver BiDi to "tentative standard". BTW, not sure if you hold some grudge against WebDriver BiDi in particular, we were merely saying "gee, I sure hope something better than WebDriver comes along, b/c E2E testing kinda sucks". > Your blog post calls it "our in-browser operating system" which is a far cry from a standard. You "team up with browser vendors directly", yet not through web standards bodies, but through some "bytecode alliance" that aims to build outside the browser. Also, unsurpisingly, zero links anywhere to an actual standards text or even to a specification of these web containers. I am not sure what your objection is. We have a product, we're describing our efforts to port it to a new browser engine.
  - dmitriid 4y ago
    I guess I didn't understand what exactly you were talking about when talking about "this new standard": WebDriver BiDi or WebContainers. WebDriver BiDi is on the standards track, that's true: https://w3c.github.io/webdriver-bidi/ https://w3c.github.io/webdriver-bidi/
    - jrvidal 4y ago
      I see, it seems we misread each other.
      - dmitriid 4y ago
        Just a regular day on HN
- md224 4y ago
  I think "this new standard" was referring to WebDriver BiDi, not WebContainers, so you might be misreading them. That being said, I agree that the blog post made it sound like WebContainers is some kind of standard, and I also found that to be confusing.
krono 4y ago
Poor choice of words on my end, apologies. The underlying technologies and the tooling that you've been building on top of it are great. I was merely pointing out the confusing or perhaps misleading writing style of this announcement.

dmitriid 4y ago

> We did mention our interest in this new standard getting more momentum You keep calling it a standard. The "working group" is some people on Discord. Your blog post calls it "our in-browser operating system" which is a far cry from a standard. You "team up with browser vendors directly", yet not through web standards bodies, but through some "bytecode alliance" that aims to build outside the browser. Also, unsurpisingly, zero links anywhere to an actual standards text or even to a specification of these web containers.

jrvidal 4y ago
> The "working group" is some people on Discord Fair enough, we should correct our mention of WebDriver BiDi to "tentative standard". BTW, not sure if you hold some grudge against WebDriver BiDi in particular, we were merely saying "gee, I sure hope something better than WebDriver comes along, b/c E2E testing kinda sucks". > Your blog post calls it "our in-browser operating system" which is a far cry from a standard. You "team up with browser vendors directly", yet not through web standards bodies, but through some "bytecode alliance" that aims to build outside the browser. Also, unsurpisingly, zero links anywhere to an actual standards text or even to a specification of these web containers. I am not sure what your objection is. We have a product, we're describing our efforts to port it to a new browser engine.
- dmitriid 4y ago
  I guess I didn't understand what exactly you were talking about when talking about "this new standard": WebDriver BiDi or WebContainers. WebDriver BiDi is on the standards track, that's true: https://w3c.github.io/webdriver-bidi/ https://w3c.github.io/webdriver-bidi/
  - jrvidal 4y ago
    I see, it seems we misread each other.
    - dmitriid 4y ago
      Just a regular day on HN
md224 4y ago
I think "this new standard" was referring to WebDriver BiDi, not WebContainers, so you might be misreading them. That being said, I agree that the blog post made it sound like WebContainers is some kind of standard, and I also found that to be confusing.

krono 4y ago

Poor choice of words on my end, apologies. The underlying technologies and the tooling that you've been building on top of it are great. I was merely pointing out the confusing or perhaps misleading writing style of this announcement.