Clipboard API 435fabe6f994
Update Privacy section
Update Privacy section
This week's Web Performance Working Group will be focused on triage. Thanks! Todd Hangout: https://hangouts.google.com/hangouts/_/chromium.org/webperf...
We'll be having our fifth scheduled teleconference of the year on
Wednesday, May 16th at 9
:00 PST, 12
:00 EST, 18
:00 CET, etc.
Merge pull request #178 from TakayoshiKochi/note Add a note about inheritance of UIEvent.
Meta: use HTTPS rather than FTP for UnicodeData.txt Fixes #141.
Be clearer on which user agents the API applies to Fixes #87.
[CSS2] readd old pre-2016 anchors See https://github.com/w3c/csswg-drafts/issues/2551; these anchors were changed in the 2016 republication of CSS 2.1 as a result of 914790fe62140c5deb389ac3dfea7b128b860fa8. This commit undoes that, and adds the 2016 anchors as a second wrapper element.
[CSS2] Update editors per Berlin F2F
[CSS2] Clarify "CSS2" to mean the 1998 REC
[CSS2] Make the spec refer to "CSS 2" generally
[CSS2] Remove the old 2.1 changes appendix
[CSS2] reword some of the 2.2 abstract this moves away from Bert's original text
[CSS2] Bump version to 2.2, change status to ED Partly based on 955261b7f6
[css2] explicitly specify what gets set to what with MCW
[css2] Fix typo See #2132
[css2] Correct misleading note This closes #1797
[css2] Linkify a mention of the
'height' property (#1532)
In section CSS2 10.3.2, there are a series of paragraphs that start out "If
'width' ..." with both properties linkified. One of them neglects to linkify 'height'. This pull request fixes that.
[css2] change w3.org logo src to https
[css2] Fix SV agreement error noticed by Kate Stamps --HG-- extra : convert_revision : svn%3A73dc7c4b-06e6-40f3-b4f7-9ed1dbc14bfc/trunk%403265
Issues ------ * w3c/page-visibility (+0/-0/💬1) 1 issues received 1 new comments: - #39 Why does visibilitychange fire after pagehide in the unload...
* w3c/presentation-api (+0/-0/💬5)
2 issues received 5 new comments:
- #449 Behavior of
window.reload() on presentation receiver page...
Hi Jeff! It might help to look at the entities and relationships involved. Ideally, the user has a relationship with the payment method provider, whic...
might we also pls add to agenda: cross-origin framing of webauthn-wielding origins (WebAuthn + Web Payments) https://lists.w3.org/Archives/Public/publ...
At BlinkOn 9 there was discussion of how ergonomics of the Worker API could be improved in ways similar to what you suggest. Video of that session is ...
Peter St. Andre replied:> On 5/14/18 5
:56 PM, =JeffH wrote:>
>> In the context of Web Payments, a "payee", aka "merchant", webapp
>> ("payee origin"...
Make changelog more explicit that this is a deferment
More explicit that hata/hatchpath are deferred
Actually spell deferred correctly
This is how HTTP referer became a thig
Naturally. I'm suggesting that might not get us where we want to go, but I suppose it's all we've got. Yes, I didn't mean to imply otherwise. Agreed. ...
Merge pull request #452 from dstorey/remove-mesh Remove mesh gradients
wrt relationship of Permissions, Feature Policy, Origin Policy, see thread here: <https://discourse.wicg.io/t/relationship-of-permissions-feature-pol...
'master' into remove-hatch
Defer hatch gradients to future version of SVG
Remove SVGCursorElement... ...and the ability to specify a cursor element from the CSS cursor property.
Hey WebAppSec, We've recently had interesting discussions about various mechanisms to restrict cross-origin resource loads (CORB, From-Origin, Sec-Met...
Update pservers example and switch to use SVG version
Update to point to SVG version of pservers_example