Comments (6)
It's also possible that we could make this a Firefox position throughout. A narrower scope might make it easier to take a position.
from standards-positions.
Even though we are all technically part of the Firefox organization, there seems to be a public expectation of a "Mozilla position on X" (as sometimes things apply more broadly than a "browser's position").
However, I don't mind if we just go with "Firefox's position" throughout - but it might still leave people wondering if that position is different from "Mozilla's position", which seems more absolute and final.
from standards-positions.
A Mozilla position seems clearer since folks are mostly looking for a position from the organization behind the browser. If at some point Mozilla becomes big enough to have multiple products with independent positions we could make it more specific, though even then it seems we should try to have positions that are consistent across products.
Anyway, I could settle for Firefox. I mostly want to remove the difference.
from standards-positions.
I concur with Anne that we should say "Mozilla". However, in cases where the distinction is relevant, we might need to just use freeform comments. I'm inclined to think that we should lean in the direction of Firefox on those. So, say for instance that there was some browser feature which Firefox was skeptical of but Servo decided to experiment with. I think we could mark this as "defer" and then have comments like ("experiments going in in other browser, including Servo may inform this position in future"). Would that work for people?
from standards-positions.
I think that's fine.
from standards-positions.
Image changed in #120.
from standards-positions.
Related Issues (20)
- `autocomplete=device-eid` and `=device-imei` HOT 3
- Digital Credentials HOT 4
- getHTML() and the serializable concept HOT 1
- CSS `@starting-style` HOT 1
- Snap Events HOT 4
- Constructors for RTC Encoded Frames with metadata HOT 1
- Importmap integrity HOT 2
- Consider adding WebKit standards-position URL to the issue template
- document.caretPositionFromPoint API in shadow DOM scenario HOT 1
- CSS Nesting: @nest HOT 5
- Reduce Accept-Language
- Web Translation API HOT 1
- AudioContext.onerror HOT 3
- Allow converting VideoFrame to RGB pixel formats by calling VideoFrame.copyTo() HOT 1
- Still on SerialPort API HOT 3
- The ChapterInformation interface HOT 3
- HTML Fullscreen Without A Gesture
- ShadowRealm API HOT 3
- Dialog light dismiss HOT 2
- WebGPU: ServiceWorker and SharedWorker support HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from standards-positions.