Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

The Mozilla issue is labeled as "Position: Positive" and there is a comment that says:

> We're supportive of View Transitions, but since it's a new capability for MPAs in particular, we think it's important that the solution works well for MPAs and that it's consistent with the solution for SPAs. As such, if design changes are needed for the MPA use case that also affect SPA API, the latter should be updated as appropriate even though it has shipped. In other words, we think it would be bad for the SPA and MPA APIs to diverge or be inconsistent.

I don't think that's undecided. More like, "positive with some reservations".

edit: When I think about it again, perhaps you are right given the issue is still open (but also "ready to add").

edit2: Thinking about it more, I like the open process and all but perhaps such discourse should be private before being finalized as early commenters from Mozilla can have a premature influence on public opinion.



> but perhaps such discourse should be private before being finalized as early commenters from Mozilla can have a premature influence on public opinion.

No, it shouldn't. It's a good thing all discussion is happening in the open. See how Firefox devs still have their reservations but Chrome already shipped it to prod completely ignoring any such reservations.


FWIW, that's a pretty standard behavior for Chrome teams) and, as far as I understand, related to how they are evaluated within Google.

More spec proposals == good for your career.

Shipping a feature (even if it's non-standard) == good for your career.

Ensuring standard-compatibility == noop.

Source: I used to be a browser dev annoyed by how Chrome kept shipping non-standard features.


That's a feature, not a bug.

As long as Chrome has > 80% market share, the more non-standard features the ship, the more they cement their position.

Same as IE6, which was intentionally non-standards. Sites would be designed to work in IE, and would not work on Netscape.

Considering how much spying and how much lock-in Chrome provides for Google, anything that makes devs design for Chrome only is a huge advantage.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: