-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WHATWG translations #1
Comments
Do-u-mo, Anne-san. Yes, it is welcom. DOM, For now, these are updated regularly to follow WHATWG’s specs, (Note: These pages have a function to switch words in Japanese to in English and vice-versa, located at the bottom-left of the window. |
Wow, you're even up to date with the latest---very large---changes to Streams! This is awesome! I'll definitely add a link from the top of Streams tomorrow. |
I have added a link to XMLHttpRequest: https://xhr.spec.whatwg.org/. If that looks good I'll add it to the remaining standards. |
See triple-underscore/triple-underscore.github.io#1 for context. Thanks @triple-underscore!
That’s ok. Looks good. |
See triple-underscore/triple-underscore.github.io#1 for more details.
See triple-underscore/triple-underscore.github.io#1 for more details.
See triple-underscore/triple-underscore.github.io#1 for more details.
See triple-underscore/triple-underscore.github.io#1 for more details.
See triple-underscore/triple-underscore.github.io#1 for more details.
Great, I think I have covered them all now. Submitted a pull request for whatwg/javascript since I'm not sure if @mathiasbynens would appreciate me editing that document directly. Thanks so much for doing this, I'm sure the Japanese community appreciates this a lot. If you translate more documents in the future, please don't hesitate to tell us about them, we'd love to work together. |
See triple-underscore/triple-underscore.github.io#1 for more details. Closes #33.
* Add more legacy event types for createEvent() Approximately as requested at https://bugzilla.mozilla.org/show_bug.cgi?id=1251198#c7. This is the list of events supported in createEvent() by at least two of Firefox, Chrome, and IE 11. The one exception is I omitted MutationEvent, which all three support, because apparently spec-land has decided to deny its existence in the hope that it will go away. Bikeshed does not know about all of the added interface names, hopefully that will sort itself out over time. * Meta: improve pull request instructions for DOM See whatwg/fetch#276 for context. * Enable an event listener to be invoked just once * Editorial: web compatibility typically remains relevant Fixes whatwg#210. * Shadow: define attachShadow() for custom elements * Meta: make it easier to reference participate in a tree PR: whatwg#216 * Define node document for new Text nodes Fixes whatwg#224 and part of whatwg#212. Also fix part of whatwg#209 by stating these algorithms can rethrow exceptions. * Use a single concept for attribute changes This setup is still a little sketchy I think, but not more so than the insertion and removing steps. * SVGEvent is only Gecko, Blink also has SVGEvents As pointed out by zcorpan in whatwg#227. * Set createDocument()'s content type based on namespace Fixes whatwg#217. PR: whatwg#218 * Make document.createEvent("touchevent") sometimes throw Browsers typically disable touch events on non-touch devices, and there exists web content that detects this difference using document.createEvent(). Fixes whatwg#227. * Shadow: define slotchange event Shadow: define slotchange event Fixes WICG/webcomponents#288. This defines the slotchange event in response to remove/insert operations, changes to a slot’s name attribute, and changes to an element’s slot attribute. This also introduces the assigned nodes concept for slots, and assigned slot concept for slotables. Slotables now also have a name, rather than a “get name”. The slotchange event dispatches just after mutation observers have their callbacks invoked. The slotchange event is not yet marked scoped as scoped events are not yet defined in the DOM Standard. Note: although the original issue did not mention it, this also suppresses signaling when slots are removed from a tree. Not just when they are inserted. * Editorial: update custom element cross-spec references * Editorial: fix a few cross-linking missteps * Editorial: make "is" and "prefix" optional in "create an element" * Use "create an element" in createHTMLDocument Takes care of part of whatwg#212. * Editorial: align exception language with IDL * Editorial: introduce more shadow-including terms for CSS Fixes whatwg#225. * Editorial: distributed -> flattened * Meta: export more terms Fixes whatwg#233. * Editorial: add "shadow host" and "assigned" as terms This makes a couple of non-null checks read better and enshrines a term we had already been using. * Editorial: flip non-null/otherwise conditions PR: whatwg#234 * Shadow: <slot> is now defined in HTML * Remove passive as event listener key This changes makes passive no longer contribute to the uniqueness of an event listener. It therefore also no longer needs to be supported as part of removeEventListener(). Fixes WICG/EventListenerOptions#27. PR: whatwg#236 * Meta: point out event's timeStamp is likely to change See whatwg#23 for details. * Add [CEReactions] annotations to mutating methods Part of WICG/webcomponents#186, and furthering whatwg/html@27aa7bc. Linking [CEREactions] will happen once speced/bikeshed#677 is fixed. * Editorial: check stop propagation flag at start of invoke * Editorial: deduplicate Veli Şenol * Editorial: define defaults for EventListenerOptions Although this is also done in prose, this nonetheless simplifies the prose a bit and makes it clearer to those skimming the standard what is going on (although skimming is not recommended). Fixes whatwg#239. * Meta: link to Japanese translation See triple-underscore/triple-underscore.github.io#1 for more details.
See triple-underscore/triple-underscore.github.io#1 for more details. Closes #33.
Added Japanese translation of Compatibility Standard: |
@miketaylr ^^ |
Whoa, awesome @triple-underscore! Just filed whatwg/compat#60 to add the link. |
Added Japanese translation of Infra Standard: |
Added Japanese translation of Storage Standard: |
Wow, thanks! Added a link: whatwg/storage@76988d2. |
Added Japanese translation of Console Standard: |
Awesome! @domfarolino, do you want to add a link to console.spec.whatwg.org? |
Sure @domenic will do thanks for the heads up! |
Added two Japanese translations of: Fullscreen API: Notifications API: |
Thanks @triple-underscore, that's great! I suspect we'll have them both linked somewhere next week. We're changing some templates around and it's a bit of a coordination puzzle so that's why there's some delay. |
Added Japanese translation of MIME sniffing: |
\o/ created whatwg/mimesniff#62 to link it. |
Added Japanese translation of Web IDL: The translation of § ECMAScript binding is separated to the latter URL. |
Thanks @triple-underscore! I'll link to the first document as I see that itself links the second document. See whatwg/webidl#1036. |
Added Japanese translation of WebSockets: |
Awesome, thank you! I sent whatwg/websockets#11, although I think the editor is still OOO for a bit. |
Added Japanese translation of File System: |
That's great! I'll link it from the specification. |
I noticed you have a great set of translations of WHATWG standards. Would you mind if they were linked from the English version? E.g., https://notifications.spec.whatwg.org/ points to a Simplified Chinese translation. It would be great for https://url.spec.whatwg.org/, https://dom.spec.whatwg.org/, etc. to point to their Japanese translation I think. What do you think?
The text was updated successfully, but these errors were encountered: