Requesting SUMO docs from Bugzilla

[Emma Humphries]

At the request of the Firefox Desktop team, we've revised how you request
user-facing docs (in SUMO) from Bugzilla.

There's a new flag, `user-doc-firefox`, available to Firefox related
products.

Its use is documented in
https://firefox-bug-handling.mozilla.org/doc-requests.

The summary is, set the flag to `docs-needed` if you think your work
requires user-facing documentation. The SUMO team will get notifications.

You can file documentation issues in
https://github.com/mozilla/firefox-bug-handling/, or ask in #bug-handling:
mozilla.org on chat.mozilla.com.

Thanks.

-- Emma
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Intent to prototype and ship: ARIA annotations

[James Teh]

In Firefox 75, we intend to enable ARIA annotations by default.

Summary: This adds two new ARIA roles, a new aria-description attribute and
expands aria-details. These changes are needed to support screen reader
accessibility of comments, suggestions and other annotations in published
documents and online word processing scenarios such as Google Docs, iCloud
Pages, and MS Office Online. This is not currently possible without
resorting to live region hacks, which are not as reliable as semantics and
do not work well with Braille displays. As a result, screen reader users
have non-optimal support for collaboration features of online word
processors.
Bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1608975
Standard: Incorporated into ARIA 1.3 editor's draft. Explainer with links
to pull requests: https://github.com/aleventhal/aria-annotations
Platform coverage: desktop
Preference: None. Because this simply exposes new values to accessibility
clients using existing accessibility APIs, we do not anticipate any
problems.
DevTools bug: None. Both the DOM inspector and accessibility inspector will
reflect this new information without any additional work.
Other browsers: Chrome shipping enabled by default in version 82:
https://chromestatus.com/feature/4666935918723072
web-platform-tests: None. ARIA WPT is still somewhat of a work in progress
and hasn't been updated for ARIA 1.2 yet, let alone 1.3. We will have Gecko
tests, though.
Secure contexts: Not restricted to secure contexts, consistent with the
rest of ARIA.
Is this feature enabled by default in sandboxed iframes?: Yes; has no
impact on sandboxed iframes.
Link to standards-positions discussion:
https://github.com/mozilla/standards-positions/issues/253
How stable is the spec: The spec is straightforward and has been reviewed
and approved by stakeholders across the accessibility industry. We do not
anticipate any fundamental changes.

Jamie
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Re: Intent to implement: Cookie SameSite=lax by default and SameSite=none only if secure

[amarchesini]

Hi everyone,

here is something more about cookies sameSite=lax by default.

In order to test this feature properly and to see the level of breakage 
introduced, we've decided to enable it in nightly.

Bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1604212

This feature is partially covered by web-platform-tests:
https://searchfox.org/mozilla-central/source/testing/web-platform/tests/cookies/samesite-none-secure
https://searchfox.org/mozilla-central/source/testing/web-platform/tests/cookies/samesite

As you know, Chrome is already rolling out this feature: it's active for 1% of 
their population.

I filed a meta bug to collect breakages - 
https://bugzilla.mozilla.org/show_bug.cgi?id=1618610
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform