This is the repository for the documentation that sits at https://w3c.github.io/.
Directories (e.g., "DOM-Level-3-Events-key") are repositories that have been renamed. These serve as redirects.
The W3C organisation
Home Page: https://w3c.github.io/
This is the repository for the documentation that sits at https://w3c.github.io/.
Directories (e.g., "DOM-Level-3-Events-key") are repositories that have been renamed. These serve as redirects.
I was reading https://annevankesteren.nl/2016/03/upstreaming-custom-elements-shadow-dom today and apparently https://w3c.github.io/webcomponents/spec/custom/ and https://w3c.github.io/webcomponents/spec/shadow/ used to be working links.
Redirecting to https://html.spec.whatwg.org/multipage/custom-elements.html and https://dom.spec.whatwg.org/#shadow-trees respectively would seem appropriate.
I read http://w3c.github.io/ and found that it lacked a clear policy on breadth of W3C Projects.
If that is indeed the case, we should clarify that W3C Projects include W3C staff selected projects as well as W3C Working (Interest) Group projects.
It is possible that we may want to assess other group's requests to host a given repository. For that, but also regardless, we should identify the owner(s) either by name or by e-mail address.
A specific concern of mine is that W3C Community Groups might expect we create repositories under the W3C organisation on GH. We have >220 CGs; that would hardly scale.
Can we remove the generated files from the repo? I noticed lots of people (including me) ended up editing the wrong files 😡. Alternatively, let's get rid of the src files - this simple site shouldn't need a build step.
Per #27 (comment), Github labels each have a color, and we should specify that for the labels here, so that issues are visually consistent across repositories.
For specs that are joint deliverables, having the "group" property in w3c.json accept an array of values rather than a single value would be good.
(of course, this may raise the question of whether to rename the field "groups" then; but I don't really care)
(Ie, on https://w3c.github.io/issue-metadata.html)
While adopting the labels, I have made two changes for the repository; I would think it is better:
hr:
for horizontal review, ms:
for milestones, etc. For consistency, I also used wr:
instead of WR-
for wide review. I think such prefixes help a lot; eg, it allows a proper alphanumeric sorting of the labels.Are we duplicating what's in https://github.com/w3c/licenses ? Those (contributing, license) should be the basis for new CG or WG repos.
From browsing or searching the https://www.w3.org/ website, there does not seem to be any way to find any information about the W3C API. It’s not discoverable. It’s not even readily findable using Google Search or other search engines.
There should be some much-easier way to help people find information about the API.
collapsing the five pairs of horizontal labels will help make this doc more usable.
for -tracker:
"Applied by WGs to bring an issue to the attention of a horizontal group. May also be applied by a horizontal group to indicate that they are interested in a discussion. Does not need to be resolved before transition."
for -needs-resolution:
"The horizontal group expects this issue to be resolved to their satisfaction before a transition. (Typically) only applied by horizontal groups, and only removed by them."
Per #27 (comment), we should try to merge @sandhawke's proposed spec labels into this repository. I'm in favor of rewriting them to lowercase-with-dashes per #25 in the process.
Hello,
I want to make a question about NFC Reader for Web Application.
Can an NFC Reader be able to read NFC Tag and return the value of that NFC Tag using web browsers?
So, the reader must be included in the website that can be used by all browsers and all smart phone systems.
There may be some other way to scan NFC tags without the inclusion of NFC Tag Readers.
I just want to get the value of this NFC Tag.
I would be pleased if you could help me with this issue.
Thank you in advance.
https://w3c.github.io/issue-metadata.html
It may replace an *-tracker label.
->
It may replace an i18n-tracker label.
And similar for a11y and privacy.
I have conducted a training on Github for participants of the WCAG and EO WGs. I guess it would be good introductory material but I don’t know where to put it at the moment.
Should we add the i18n language enablement labels (like i18n-alreq
, see the CSS repo for examples) to hr-labels.json?
Adding some pages on how groups and chairs can help participants from countries across the world be more involved in their working groups and across W3C. Judy Zhu had a fantastic presentation on this - we could use most of this content and some more.
Could include a page on being an AC, the AC role, things they need to know.
There are usage recommendations for GitHub labels. Should there be recommendations for issue and pull request titles? (editors on my CG was recently asking themselves this question)
Examples I've seen in the wild:
[module-name] Discussion specific to a single module
[module-name,other-module-name] Discussion related to multiple modules
General discussion or question
Ideally, we'd document the reasoning behind these recommendations (see draft below).
Curious to hear what other folks think.
DRAFT Proposal:
Why use prefixes, when labels can do the same job? Both are useful, here are a few reasons to use prefixes in issue titles:
[prefix]
is a useful visual hint when scanning a long list of issuesScreen capture showing an issue without a prefix in its title. The user has to hover it to reveal the label, and understand that it has to do with the format
module. Had it been prefixed with [format]
, the user would have immediately known about what module this issue touches on.
todo
todo
Please replace the individual doc links with a link to https://www.w3.org/wiki/DocumentReview#How_to_get_horizontal_review
That way, we reduce the maintenance burden when we update these docs.
Left- and right- margins are fixed at 20px
when width ≤ 840px
. If the window becomes slightly wider (and especially if vertical scroll bars are visible), margins actually shrink and snap down to ≃ 13px
(depends on the UA). That is not the intended behaviour.
It'd be truly awesome if the w3c github could have a favicon like [1]. If a distinction with the official www.w3.org is needed, we could make a local variation with a red background etc.
In implementation, there are a number of cases where there is implementation but it isn't interoperable. At least in HTML I have found it very useful to have a label specifically for this.
What license is this content? MIT? GPL?
A bunch of repos already have shortName
in w3c.json:
https://github.com/immersive-web/webxr/blob/master/w3c.json
https://github.com/immersive-web/webxr-ar-module/blob/master/w3c.json
https://github.com/immersive-web/webxr-gamepads-module/blob/master/w3c.json
https://github.com/w3c/accelerometer/blob/master/w3c.json
https://github.com/w3c/alt-techniques/blob/gh-pages/w3c.json
https://github.com/w3c/ambient-light/blob/gh-pages/w3c.json
https://github.com/w3c/battery/blob/gh-pages/w3c.json
https://github.com/w3c/beacon/blob/gh-pages/w3c.json
https://github.com/w3c/clipboard-apis/blob/master/w3c.json
https://github.com/w3c/danmaku/blob/master/w3c.json
https://github.com/w3c/device-memory/blob/master/w3c.json
https://github.com/w3c/deviceorientation/blob/master/w3c.json
https://github.com/w3c/did-core/blob/master/w3c.json
https://github.com/w3c/did-rubric/blob/master/w3c.json
https://github.com/w3c/did-test-suite/blob/master/w3c.json
https://github.com/w3c/did-use-cases/blob/master/w3c.json
https://github.com/w3c/DOM-Parsing/blob/gh-pages/w3c.json
https://github.com/w3c/dpub-pwp-arch/blob/gh-pages/w3c.json
https://github.com/w3c/dpub-pwp-loc/blob/gh-pages/w3c.json
https://github.com/w3c/dpub-pwp-ucr/blob/gh-pages/w3c.json
https://github.com/w3c/EasyChecks/blob/master/w3c.json
https://github.com/w3c/editing/blob/gh-pages/w3c.json
https://github.com/w3c/epub4/blob/master/w3c.json
https://github.com/w3c/FileAPI/blob/master/w3c.json
https://github.com/w3c/gamepad/blob/gh-pages/w3c.json
https://github.com/w3c/gyroscope/blob/master/w3c.json
https://github.com/w3c/hr-time/blob/gh-pages/w3c.json
https://github.com/w3c/html-aam/blob/gh-pages/w3c.json
https://github.com/w3c/html-aria/blob/gh-pages/w3c.json
https://github.com/w3c/html-extensions/blob/gh-pages/w3c.json
https://github.com/w3c/image-resource/blob/master/w3c.json
https://github.com/w3c/input-events/blob/gh-pages/w3c.json
https://github.com/w3c/IntersectionObserver/blob/master/w3c.json
https://github.com/w3c/json-ld-syntax/blob/master/w3c.json
https://github.com/w3c/longtasks/blob/master/w3c.json
https://github.com/w3c/low-vision-a11y-tf/blob/gh-pages/w3c.json
https://github.com/w3c/low-vision-SC/blob/master/w3c.json
https://github.com/w3c/magnetometer/blob/master/w3c.json
https://github.com/w3c/manifest/blob/gh-pages/w3c.json
https://github.com/w3c/me-cloud-browser/blob/gh-pages/w3c.json
https://github.com/w3c/me-media-timed-events/blob/master/w3c.json
https://github.com/w3c/media-and-entertainment/blob/master/w3c.json
https://github.com/w3c/mediacapture-depth/blob/gh-pages/w3c.json
https://github.com/w3c/mediacapture-fromelement/blob/gh-pages/w3c.json
https://github.com/w3c/mediacapture-image/blob/master/w3c.json
https://github.com/w3c/mediacapture-main/blob/master/w3c.json
https://github.com/w3c/mediacapture-output/blob/master/w3c.json
https://github.com/w3c/mediacapture-record/blob/master/w3c.json
https://github.com/w3c/mediacapture-screen-share/blob/gh-pages/w3c.json
https://github.com/w3c/mixedreality/blob/master/w3c.json
https://github.com/w3c/Mobile-A11y-TF-Note/blob/gh-pages/w3c.json
https://github.com/w3c/navigation-timing/blob/gh-pages/w3c.json
https://github.com/w3c/network-error-logging/blob/gh-pages/w3c.json
https://github.com/w3c/orientation-sensor/blob/master/w3c.json
https://github.com/w3c/page-visibility/blob/gh-pages/w3c.json
https://github.com/w3c/paint-timing/blob/master/w3c.json
https://github.com/w3c/payment-method-credit-transfer/blob/gh-pages/w3c.json
https://github.com/w3c/performance-timeline/blob/gh-pages/w3c.json
https://github.com/w3c/permissions/blob/master/w3c.json
https://github.com/w3c/pointerevents/blob/gh-pages/w3c.json
https://github.com/w3c/pointerlock/blob/gh-pages/w3c.json
https://github.com/w3c/preload/blob/gh-pages/w3c.json
https://github.com/w3c/presentation-api/blob/gh-pages/w3c.json
https://github.com/w3c/proximity/blob/gh-pages/w3c.json
https://github.com/w3c/push-api/blob/gh-pages/w3c.json
https://github.com/w3c/remote-playback/blob/gh-pages/w3c.json
https://github.com/w3c/reporting/blob/master/w3c.json
https://github.com/w3c/requestidlecallback/blob/gh-pages/w3c.json
https://github.com/w3c/resource-hints/blob/gh-pages/w3c.json
https://github.com/w3c/resource-timing/blob/gh-pages/w3c.json
https://github.com/w3c/screen-orientation/blob/gh-pages/w3c.json
https://github.com/w3c/selection-api/blob/gh-pages/w3c.json
https://github.com/w3c/sensors/blob/master/w3c.json
https://github.com/w3c/server-timing/blob/gh-pages/w3c.json
https://github.com/w3c/svgwg/blob/master/w3c.json
https://github.com/w3c/tv-ggie/blob/master/w3c.json
https://github.com/w3c/UAAG/blob/gh-pages/w3c.json
https://github.com/w3c/uievents/blob/gh-pages/w3c.json
https://github.com/w3c/uievents-code/blob/gh-pages/w3c.json
https://github.com/w3c/uievents-key/blob/gh-pages/w3c.json
https://github.com/w3c/user-timing/blob/gh-pages/w3c.json
https://github.com/w3c/using-aria/blob/gh-pages/w3c.json
https://github.com/w3c/vc-data-model/blob/gh-pages/w3c.json
https://github.com/w3c/vc-imp-guide/blob/gh-pages/w3c.json
https://github.com/w3c/vc-test-suite/blob/gh-pages/w3c.json
https://github.com/w3c/vc-use-cases/blob/gh-pages/w3c.json
https://github.com/w3c/voiceinteraction/blob/master/w3c.json
https://github.com/w3c/wai-accessibility-principles/blob/master/w3c.json
https://github.com/w3c/wai-bcase/blob/master/w3c.json
https://github.com/w3c/wai-contacting-orgs/blob/master/w3c.json
https://github.com/w3c/wai-develop-training/blob/master/w3c.json
https://github.com/w3c/wai-eval-report-templates/blob/master/w3c.json
https://github.com/w3c/wai-first-aid/blob/master/w3c.json
https://github.com/w3c/wai-inclusion/blob/gh-pages/w3c.json
https://github.com/w3c/wai-intro-accessibility/blob/gh-pages/w3c.json
https://github.com/w3c/wai-InvolveUsersAll/blob/master/w3c.json
https://github.com/w3c/wai-InvolveUsersEval/blob/master/w3c.json
https://github.com/w3c/wai-mobile/blob/master/w3c.json
https://github.com/w3c/wai-org-policies/blob/master/w3c.json
https://github.com/w3c/wai-people-use-web/blob/master/w3c.json
https://github.com/w3c/wai-presentations2all/blob/master/w3c.json
https://github.com/w3c/wai-quick-start/blob/master/w3c.json
https://github.com/w3c/wai-selecting-eval-tools/blob/master/w3c.json
https://github.com/w3c/wai-shared-experiences/blob/master/w3c.json
https://github.com/w3c/wai-std-harmonization/blob/master/w3c.json
https://github.com/w3c/wai-tutorial-images/blob/master/w3c.json
https://github.com/w3c/wai-wcag-mob-overlap/blob/master/w3c.json
https://github.com/w3c/wake-lock/blob/gh-pages/w3c.json
https://github.com/w3c/web-share/blob/master/w3c.json
https://github.com/w3c/web-thing-protocol/blob/master/w3c.json
https://github.com/w3c/webappsec-clear-site-data/blob/master/w3c.json
https://github.com/w3c/webappsec-cowl/blob/master/w3c.json
https://github.com/w3c/webappsec-credential-management/blob/master/w3c.json
https://github.com/w3c/webappsec-csp/blob/master/w3c.json
https://github.com/w3c/webappsec-mixed-content/blob/master/w3c.json
https://github.com/w3c/webappsec-referrer-policy/blob/master/w3c.json
https://github.com/w3c/webappsec-secure-contexts/blob/master/w3c.json
https://github.com/w3c/webappsec-trusted-types/blob/master/w3c.json
https://github.com/w3c/webappsec-uisecurity/blob/master/w3c.json
https://github.com/w3c/webappsec-upgrade-insecure-requests/blob/master/w3c.json
https://github.com/w3c/webauthn/blob/master/w3c.json
https://github.com/w3c/webcomponents/blob/gh-pages/w3c.json
https://github.com/w3c/webcrypto/blob/master/w3c.json
https://github.com/w3c/webdriver/blob/master/w3c.json
https://github.com/w3c/webpayments/blob/gh-pages/w3c.json
https://github.com/w3c/webpayments-flows/blob/gh-pages/w3c.json
https://github.com/w3c/webpayments-http-messages/blob/gh-pages/w3c.json
https://github.com/w3c/webpayments-methods-tokenization/blob/gh-pages/w3c.json
https://github.com/w3c/webpayments-overview/blob/gh-pages/w3c.json
https://github.com/w3c/webrtc-pc/blob/master/w3c.json
https://github.com/w3c/webrtc-stats/blob/master/w3c.json
https://github.com/w3c/webvtt/blob/gh-pages/w3c.json
https://github.com/w3c/wot-architecture/blob/master/w3c.json
https://github.com/w3c/wot-binding-templates/blob/master/w3c.json
https://github.com/w3c/wot-profile/blob/master/w3c.json
https://github.com/w3c/wot-scripting-api/blob/master/w3c.json
https://github.com/w3c/wot-security/blob/master/w3c.json
https://github.com/w3c/wot-security-best-practices/blob/master/w3c.json
https://github.com/w3c/wot-security-testing-plan/blob/master/w3c.json
https://github.com/w3c/wot-thing-description/blob/master/w3c.json
https://github.com/w3c/xinclude/blob/master/w3c.json
https://github.com/WICG/BackgroundSync/blob/master/w3c.json
https://github.com/WICG/cors-rfc1918/blob/master/w3c.json
https://github.com/WICG/encrypted-media/blob/master/w3c.json
https://github.com/WICG/entries-api/blob/master/w3c.json
https://github.com/WICG/focus-visible/blob/master/w3c.json
https://github.com/WICG/get-installed-related-apps/blob/master/w3c.json
https://github.com/WICG/InputDeviceCapabilities/blob/gh-pages/w3c.json
https://github.com/WICG/interventions/blob/master/w3c.json
https://github.com/WICG/netinfo/blob/gh-pages/w3c.json
https://github.com/WICG/origin-policy/blob/master/w3c.json
https://github.com/WICG/overscroll-scrollend-events/blob/gh-pages/w3c.json
https://github.com/WICG/ResizeObserver/blob/master/w3c.json
https://github.com/WICG/scroll-animations/blob/master/w3c.json
https://github.com/WICG/web-share-target/blob/master/w3c.json
https://github.com/WICG/webusb/blob/master/w3c.json
This should be documented in https://w3c.github.io/w3c.json.html.
We should update the logo at the bottom of https://w3c.github.io/ to the new logo.
We have (a small number of) Member-only repos as well as tooling that works better when individuals link their W3C user account with their GitHub account.
We should document early in the "how do I get started?" search path, e.g. on W3C on GitHub that one ought to link one's GitHub account in their W3C user profile.
There is some value already in converging in the format of commit messages alone.
But also, by doing that, we could at some point adopt tools that process and digest the commit history of a project to produce automated changelogs and/or decide the next semantic version to be published (eg, semantic-release).
This is done in a number of redirects and won't actually work:
w3c.github.io/webvr/index.html
Line 7 in da86889
The expression is a function, but the function isn't invoked. In other redirects the function expression is wrapped in (func)()
.
@dontcallmedom can you take a look?
I don't understand the difference between substantive and bug. Also, all changes are presumably enhancements, so I'm not sure what the purpose of that is, and it lacks clarity on whether it means editorial or substantive change.
index.html should include a direct link to https://github.com/w3c/ash-nazg because it is totally unfindable otherwise
(hence various misspellings / misspeakings of it included in issue name in order to increase websearch findability)
From @tobie :
It would be nice to have a bit more consistency (sometimes you're using ":" as a namespace, sometimes, using spaces, sometimes dashes). I'd also recommend avoiding whitespace, which makes searching more complicated (you have to quote labels) and URLs less user friendly (%20 everywhere), but that's a minor issue.
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.