Re: Intent to ship: Return pixel deltas in wheel event if deltaMode is not checked by authors

On 09/03/2021 18:21, Emilio Cobos Álvarez wrote: On 3/9/21 17:10, Anne van Kesteren wrote: On Tue, Mar 9, 2021 at 4:45 PM Emilio Cobos Álvarez wrote: Let me know if you have any concerns with this or what not. So if I understand it correctly we'll have a getter with side effects. Is the ex

web-platform-tests tracing/debugging improvements

A couple of wpt changes recently landed that might be of interest to people: * testharness.js tests now trace the individual asserts that run (for performance reasons this only happens when output is enabled e.g. when only a single test is run locally). * A --debug-test command line option ha

Re: Intent to ship: remote-protocol (CDP)

On 12/01/2021 16:56, Anne van Kesteren wrote: On Tue, Jan 12, 2021 at 5:43 PM James Graham wrote: CDP is not part of any web standard, and is not exposed to content. Seems unfortunate we cannot standardize on this format if we have to support it anyway, but I guess that was already

Intent to ship: remote-protocol (CDP)

Summary: remote-protocol provides a Firefox implementation of a subset of the Chrome DevTools Protocol (CDP) [1], specifically targeted at testing and automation use cases. remote-protocol isn't a web-exposed feature so it doesn't fit into the standard exposure guidelines. However we're mentio

This year in web-platform-tests - 2020 Edition

It's been a long year hasn't it? Maybe the next one will seem shorter. Although, at home in London today, it feels that if it does, it will only be for want of a leap day. Given all that's passed since 2019, you would be forgiven for having entirely forgotten about "This Year in Web-Platform-Test

Re: web-platform-tests now runs under Python 3

On 15/12/2020 20:00, James Graham wrote: With bug 1678663 [1] now on central, web-platform-tests uses Python 3, both locally under mach, and on Gecko CI. This matches upstream, where the CI switched over a few weeks ago [2] and Google's CI which switched at the end of last week. Appar

web-platform-tests now runs under Python 3

With bug 1678663 [1] now on central, web-platform-tests uses Python 3, both locally under mach, and on Gecko CI. This matches upstream, where the CI switched over a few weeks ago [2] and Google's CI which switched at the end of last week. For most users this change should be entirely transpare

Re: HTTP/3 ready for testing

On 20/11/2020 16:09, Dragana Damjanovic wrote: Our implementation is ready for testing. What's the interop testing story for HTTP/3? How confident are we that we won't run into implementation differences that look like web-compat issues? Also, what's the priority on enabling other test typ

Accessibility review process

(Also cross-posting to firefox-dev.) Hi all, Tl;dr: The Mozilla Accessibility Release Guidelines outline what is needed to make user interfaces accessible to people with disabilities. If you would like help from the accessibility team to determine whether your change is accessible, you can now se

Re: Status of Ubuntu 20.04 as a development platform

On 10/11/2020 14:17, Kyle Huey wrote: On Tue, Nov 10, 2020 at 3:48 AM Henri Sivonen wrote: Does Ubuntu 20.04 work properly as a platform for Firefox development? That is, does rr work with the provided kernel and do our tools work with the provided Python versions? rr works. I use 20.04 pers

Re: Writing web-platform-tests using non-web-exposed APIs is now easier

On 26/10/2020 14:11, Mirko Brodesser wrote: Supporting synthesizing drag-and-drop events [1] That seems like the kind of thing that ought to be covered by testdriver. Would something like new test_driver.Actions() .pointerMove(0,0,{origin:elem1}) .pointerDown() .pointerMove(0,0,{origin

Writing web-platform-tests using non-web-exposed APIs is now easier

Two changes that recently landed in web-platform-tests make it easier to write tests that require access to non-web-exposed features: * testdriver APIs now work in many situations involving multiple browsing contexts origins * SpecialPowers is now available in gecko-only web-platform-tests t

Re: Adopting the black Python code style

On 19/10/2020 22:01, Jeff Gilbert wrote: I'm disappointed by that. FWIW last time I looked at black, I found that the compromises it made to be fully automatic and with minimal configuration meant that it was liable to produce ugly or difficult to read code in some situations. I understand

[action maybe required] Verify recent wpt changes are still on autoland

A bug in the wptsync when switching over to Python 3 caused it to drop some upstream changes when doing recent landings. In order to get things back on track I've made a patch which copies over the files from the current sync revision from GitHub to m-c and reapples changes made to mozilla-cent

Re: Intent to ship in Nightly channel and early Beta: `beforeinput` event and `InputEvent.getTargetRanges()`

On 17/09/2020 17:14, Masayuki Nakano wrote: web-platform-tests: none for `beforeinput` (because of it requires user input, and test driver was not when other browsers implement it), but there are a lot of tests for `getTargetRanges()` which I added (200+). https://searchfox.org/mozilla-central/

Re: Searchfox now gives info about tests at the top of test files!

This is awesome! On 28/07/2020 18:40, Andrew Sutherland wrote: - How long your tests take to run (on average)! - How many times your tests were run in the preceding 7 days[1]! - How many times your tests were skipped in the preceding 7 days! - What skip-patterns govern the skips from your test's

Print reftest support in wpt

It is now* possible to write reftests for print layout in wpt. These work like normal reftests except instead of comparing the rendering of two documents in a browser window, they compare all the pages of a paginated rendering of the documents. wpt print reftests go through the full printing m

Re: Intent to change default try selector from `syntax` to `auto` (ACTION NEEDED for try syntax users)

On 06/07/2020 17:50, Tom Ritter wrote: Thank you for continuing to keep try syntax working. I know I'm holding back progress by not spending the time to figure out how to convert `./mach try -b do -p win32-mingwclang,win64-mingwclang -u all -t none` to fuzzy (maybe it's something like `./mach tr

Re: Intent to Ship : HTML5 element (Nightly Only)

While this doesn't need to block shipping in Nightly, I think we should consider advocating for the focus behaviour to be changed (and changing it in Firefox if we can get it into the spec) before we ship to release. The currently specified behaviour (and what both Firefox and Chrome implement) is

Re: Proposal: remove support for running desktop Firefox in single-process mode (e10s disabled) anywhere but in tests

In general, this obviously makes a lot of sense. However, because there is so much extra complication for accessibility when e10s is enabled, I find myself disabling e10s in local opt/debug builds to isolate problems to the core a11y engine (vs the a11y e10s stuff). The ability to do this was instr

Re: Intent to ship: ParentNode#replaceChildren

On 25/05/2020 16:45, Alex Vincent wrote: Effective 2020-05-27, I intend to land ParentNode.replaceChildren feature in mozilla-central, on by default. This has not been developed behind a preference, as both I and the reviewers believe this is a small change. Status in other browsers is unimplemen

Re: Testing Rust code in tree

On 11/05/2020 23:54, Mike Hommey wrote: On Mon, May 11, 2020 at 03:37:07PM -0700, Dave Townsend wrote: Do we have any standard way to test in-tree Rust code? Context: We're building a standalone binary in Rust that in the future will be distributed with Firefox and of course we want to test it.

Intent to prototype and ship: ARIA annotations

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 an

Re: Intent to prototype and ship: CSS comparison functions: min() / max() / clamp()

On 21/02/2020 01:42, Emilio Cobos Álvarez wrote: web-platform-tests: There's a variety of tests in: https://wpt.fyi/results/css/css-values?label=master&label=experimental&aligned&q=minmax%7Cclamp Do we have any sense of how good the test coverage is? Also, not having enabled causes some confu

Re: Intent to implement: CSS conic-gradient

On 16/02/2020 10:46, Tim Nguyen wrote: web-platform-tests: https://searchfox.org/mozilla-central/search?q=conic-gradient&case=false®exp=false&path=testing%2Fweb-platform That looks like some tests for the parsing, but afaict not much for rendering. Do we have a sense of how good the test cove

Re: Intent to Deploy: ThreadSanitizer

On 04/02/2020 09:41, Christian Holler wrote: One of the problems with deploying ThreadSanitizer in CI is that we have a fair amount of existing data races that orange pretty much every test we have. In order to solve this situation, we are currently working on the following strategy: 1.

Re: Intent to implement: AVIF (AV1 Image Format) support

On 13/01/2020 21:48, Jon Bauman wrote: AVIF is an image format based on the AV1 video codec [1] from the Alliance for Open Media [2]. AV1 support shipped in release 55 [3] and is currently supported in Chrome, but not Safari. There is an open issue for AVIF support in Chrome [4]. Bug: https://bu

Re: Visibility of disabled tests

On 09/01/2020 10:46, David Burns wrote: I think a lot of the problem is not necessarily a technical issue, meaning I am not sure that tooling will solve the problem, but it is more of a social problem. To exapnd a little on this; we've had various attempts at making disabled tests more visibl

Re: Intent to Prototype: beforeinput event (disabled by default even in Nightly channel)

On 08/01/2020 09:54, Masayuki Nakano wrote: Summary: "beforeinput" event is useful for web apps which manage input data into ``, `` and/or `contenteditable`. This event is fired before our editor modifies value or DOM tree and some types are cancelable. Therefore, if some user inputs are not

Re: Visibility of disabled tests

On 07/01/2020 13:29, Johann Hofmann wrote: /For disabling tests, review from the test author, triage owner or a component peer is required. If they do not respond within 2? business days or if the frequency is higher than x, the test may be disabled without their consent, but the triage own

This year in web-platform-tests - 2019 edition

Welcome to "This year in web-platform-tests"; possibly the lowest frequency regular project update at Mozilla. In a break from tradition the MoCo All Hands moving to January means that this is the first edition to come from a normal office and not a hotel corridor somewhere in North America. T

Re: Intent to prototype: CSS property `text-underline-position`

On 03/12/2019 17:50, Jonathan Kew wrote: web-platform-tests: https://wpt.fyi/results/css/css-text-decor/parsing?label=master&q=text-underline-position That looks like it's just testing the property computation. Do we also have tests for the layout effect, or is that difficult to do in this c

Re: Reminder: Planned Taskcluster migration this weekend (Nov 9)

On 04/11/2019 22:00, Chris Cooper wrote: tl;dr: Taskcluster, the platform supporting Firefox CI, will be moving to a new hosting environment during the tree closing window (TCW) this coming Saturday, Nov 9. Trees will be closed from 14:00 UTC to 23:00 UTC. CI services will be available as soo

Re: Intent to ship: CSS subgrid

On 22/10/2019 00:07, L. David Baron wrote: On Monday 2019-10-21 16:01 -0500, Mike Taylor wrote: Hi David, On 10/21/19 7:22 AM, L. David Baron wrote: (That we haven't applied the policy that much because we've granted exceptions because other browsers have shipped the features reduces the effec

Intent to remove: Fennec

frontend and any platform code that needed to disambiguate Fennec from GeckoView at runtime[0] will be targeted. Thanks, James [0] https://searchfox.org/mozilla-central/search?q=jni%3A%3AIsFennec&path= ___ dev-platform mailing list dev-plat

Re: PSA: Improvements to infrastructure underpinning `firefox-source-docs`

On 27/08/2019 16:24, Andrew Halberstadt wrote: RST is foreign to most It turns out* that firefox-source-docs also supports markdown format, so if you have existing docs in that format, or simply feel like needing to learn ReST is a significant impediment to writing docs, that option is availab

Re: Support for annotating intermittent tests with multiple statuses

On 25/07/2019 20:39, Andrew Halberstadt wrote: Excellent work Nikki! This will give us more tools to help with the war on orange. Are there plans (or at least bugs on file) to support other harnesses? I'll file some bugs. On Thu, Jul 25, 2019 at 2:47 PM James Graham <m

Support for annotating intermittent tests with multiple statuses

Thanks to the amazing work of Outreachy participant Nikki Sharpley, our test result logging infrastructure now supports marking tests as having multiple expected statuses. This can be used instead of disabling tests where the results are intermittent. Harness-level support is currently availabl

Re: Intent to ship: Visual Viewport API on Android

On 10/05/2019 21:49, David Burns wrote: Not yet as we are stabilising tests for gecko view but hopefully soon! That won't automatically work; we'd need to start uploading Android results to wpt.fyi. Which is possible in one of two ways: * Add Geckoview on Android to the TC configuration fo

Re: Lack of browser mochitests in non-e10s configuration and support for turning off e10s on desktop going forward

On 25/04/2019 17:12, Bobby Holley wrote: On Thu, Apr 25, 2019 at 3:36 AM Joel Maher wrote: On Wed, Apr 24, 2019 at 1:39 PM Bobby Holley wrote: Thanks Mike! So Fennec is the last remaining non-e10s configuration we ship to users. Given that Fennec test coverage is somewhat incomplete,

Re: PSA: web-platform-tests (dashboard | fuzzy-reftests | reftest comparisons)

On 16/04/2019 12:17, Anne van Kesteren wrote: On Mon, Apr 15, 2019 at 7:16 PM Jonathan Watt wrote: These are all really great. Thanks, James! Indeed, thanks a lot for working on this! This will help a lot with prioritizing work and also with standards development. Some feedback for the

PSA: web-platform-tests (dashboard | fuzzy-reftests | reftest comparisons)

There have been a few recent changes related to wpt that may be of interest to a wider audience; for brevity I'm coalescing them into a single email: * New wpt dashboard focused on interop problems * Support for fuzzy annotations in reftests * Better support for debugging failing reftests on wp

Re: Creating a new mach command for adding tests

On 11/04/2019 18:22, Brian Grinstead wrote: This has now landed (with initial support for xpcshell, mochitests, and web platform tests). Thanks to Andrew Halberstadt and James Graham for improving upon the initial prototype and making it easier to extend to new suites. Eager users should

Re: Proposal to remove unnecessary [type] attributes on script tags in mozilla-central

On 09/04/2019 10:31, Anne van Kesteren wrote: On Tue, Apr 9, 2019 at 5:56 AM Cameron McCormack wrote: On Tue, Apr 9, 2019, at 1:39 PM, Brian Grinstead wrote: I'd like to rewrite markup in the tree to avoid using the [type] attribute on

Re: Creating a new mach command for adding tests

On 02/04/2019 19:11, Brian Grinstead wrote: I don't think that having papercuts in the workflow for writing one type of test is the right way to nudge developers into writing another type. It also doesn't seem effective - otherwise people would be using the wpt-create tool to avoid jumping thr

Re: Creating a new mach command for adding tests

On 01/04/2019 23:13, Steve Fink wrote: On 4/1/19 11:36 AM, Brian Grinstead wrote: Based on my own experience and discussions with others, the workflow for adding new mochitests isn't great. Commonly, it looks like: "copy/paste a test in the same directory, add the new test to the relevant mani

Re: Intent to ship: CSS Containment

On 18/03/2019 19:01, Daniel Holbert wrote: As of today (March 18th 2019), I intend to turn CSS Containment on by default on all platforms, in Firefox Nightly 68. It has been developed behind the 'layout.css.contain.enabled' preference. Apologies if I've m

Re: Intent to implement: Limit the maximum life-time of cookies set through document.cookie to seven days

On 08/03/2019 15:06, Boris Zbarsky wrote: On 3/7/19 7:31 PM, Ehsan Akhgari wrote: *web-platform-tests*: This is an intervention which different engines do not agree on yet.  Creating a web-platform-test for it would be very simple but it will be failing in the engines that do not agree with th

Re: Searchfox support for mobile/android just got a little better

Really great, thanks! James On Thu, Feb 28, 2019 at 11:49 AM Kartikaya Gupta wrote: > As of today Searchfox is providing C++/Rust analysis for > Android-specific code. So stuff in widget/android and behind android > ifdefs should be turning up when you search for symbols. Note tha

Re: Intent to implement and ship: Gamepad Extensions `multi touch` and `light indicator`

On 26/02/2019 22:49, d...@mozilla.com wrote: On Tuesday, February 26, 2019 at 2:15:57 AM UTC-8, James Graham wrote: On 25/02/2019 19:44, Daosheng Mu wrote: web-platform-tests: none exist (and I don't plan to write WPTs but we do have gamepad mochitest, I will add new tests to cover

Re: Intent to implement and ship: Gamepad Extensions `multi touch` and `light indicator`

On 25/02/2019 19:44, Daosheng Mu wrote: web-platform-tests: none exist (and I don't plan to write WPTs but we do have gamepad mochitest, I will add new tests to cover these two new APIs.) Why do you plan to not write web-platform-tests? I imagine there may be technical challenges, but we s

Re: Proposal to adjust testing to run on PGO builds only and not test on OPT builds

On 21/01/2019 10:18, Jan de Mooij wrote: On Fri, Jan 18, 2019 at 10:36 PM Joel Maher wrote: Are there any concerns with this latest proposal? This proposal sounds great to me. Thank you! +1. This seems like the right first step to me. ___ dev-pl

Re: Proposal to adjust testing to run on PGO builds only and not test on OPT builds

On 17/01/2019 16:42, jmaher wrote: Following up on this, thanks to Chris we have fast artifact builds for PGO, so the time to develop and use try server is in parity with current opt solutions for many cases (front end development, most bisection cases). Even as someone not making frequent ch

Re: Proposal to adjust testing to run on PGO builds only and not test on OPT builds

On 03/01/2019 18:16, Steve Fink wrote: Good points, but given that most failures will show up debug builds, it seems like a more relevant metric is the difference between time(Opt) vs min(time(debug), time(PGO)). Though debug builds may run slow enough that it boils down to what you said? Lo

Re: Proposal to adjust testing to run on PGO builds only and not test on OPT builds

On 03/01/2019 16:17, jmaher wrote: What are the risks associated with this? 1) try server build times will increase as we will be testing on PGO instead of OPT 2) we could miss a regression that only shows up on OPT, but if we only ship PGO and once we leave central we do not build OPT, this is

Re: Intent to implement and ship: Overflow media queries

On 23/12/2018 10:59, Emilio Cobos Álvarez wrote: web-platform-tests: Minimal parsing tests are being added to:   https://wpt.fyi/results/css/mediaqueries/test_media_queries.html Unfortunately WPT has no way to test print preview or pagination right now so the rest of reftests are Gecko-only.

Next Year in web-platform-tests - 2018/19 Edition

Following the summary of what we've achieved in the previous year in web-platform-tests, I'd like to set out the plan for priorities in the coming year, and solicit feedback. There are several key things that we would like to achieve over the course of the year: * Give the platform team and

This year in web-platform-tests - 2018 edition

Welcome to the second annual update on progress in cross-browser interop testing through web-platform-tests. This year has seen big improvements to the platform coverage of wpt, as well as increasing the number of features that can be tested with wpt, and the visibility of test results in Gecko

Re: Intent to ship: set keyCode or charCode of "keypress" event to the other's non-zero value

On 04/12/2018 02:23, Masayuki Nakano wrote: On 2018/11/30 20:42, James Graham wrote: On 30/11/2018 01:37, Masayuki Nakano wrote: web-platform-tests: N/A due to requiring user input, but we have mochitests with synthesized events. I think it should be possible to write web-platform-tests for

Re: Intent to ship: set keyCode or charCode of "keypress" event to the other's non-zero value

On 30/11/2018 01:37, Masayuki Nakano wrote: web-platform-tests: N/A due to requiring user input, but we have mochitests with synthesized events. I think it should be possible to write web-platform-tests for this kind of thing now, using the testdriver API and in particular the actions support

Re: Workflow Apropos!

On 28/11/2018 20:15, Mark Côté wrote: We're still working through a longer-term vision that we'll share early next year, but I can answer some questions now. Thanks, this is helpful! * Have to make a choice early on about whether to learn a relatively unfamiliar (to the majority of de

Re: Workflow Apropos!

On 27/11/2018 17:46, Kim Moir wrote: Speeding up moz-phab moz-phab[2] is Engineering Workflow’s officially supported custom command-line interface to Phabricator, built in order to better support the “stacked commits” workflow that is common in Firefox engineering. Unfortunately some of the des

Re: Announcing new test platform "Android 7.0 x86"

This should be running GeckoView in e10s mode. We only support one child process right now, but we may try to increase that soonish. Resource consumption is a big concern. The parent process is shared with the host application right now, but we would like to split that out as well. James On Fri

Re: Intent to implement and ship: Unprefix -moz-user-select, unship mozilla-specific values.

On 11/11/2018 17:57, Emilio Cobos Álvarez wrote: web-platform-tests: Test coverage for all the values is pre-existing. There's unfortunately little coverage in WPT, but a lot in our selection and contenteditable tests. Can we upstream some of these tests to wpt? I don't know if there are/wer

Re: Intent to implement: Support Referrer Policy for

On 01/11/2018 11:03, Thomas Nguyen wrote: The link https://searchfox.org/mozilla-central/search?q=script-tag%2Finsecure-protocol.keep-origin-redirect.http.html&path= is not covered all the tests. Thanks James for pointing it out. In fact, we have synced all script-tag tests which were adde

Re: Intent to implement: Support Referrer Policy for

On 31/10/2018 14:03, Thomas Nguyen wrote: Summary: This implementation adds Referrer Policy support to the

Re: web-platform-tests that fail only in Firefox (from wpt.fyi data)

On 17/10/2018 10:12, James Graham wrote: On 17/10/2018 01:23, Emilio Cobos Álvarez wrote: Hi Philip, Do you know how do reftests run in order to get that data? I'm particularly curious about this Firefox-only failure:    css/selectors/selection-image-001.html It passes both o

Re: web-platform-tests that fail only in Firefox (from wpt.fyi data)

On 17/10/2018 01:23, Emilio Cobos Álvarez wrote: Hi Philip, Do you know how do reftests run in order to get that data? I'm particularly curious about this Firefox-only failure:   css/selectors/selection-image-001.html It passes both on our automation and locally. I'm curious because I was t

Re: Multi-browser web-platform-tests results dashboard

On 03/10/2018 13:32, Boris Zbarsky wrote: On 10/3/18 5:21 AM, James Graham wrote: So the net effect of all this is that bug fixes won't appear on the dashboard until the first upstream wpt commit after they are present in a nightly release. Right. I assume for now the volume of commi

Re: Multi-browser web-platform-tests results dashboard

On 02/10/2018 21:27, Boris Zbarsky wrote: On 10/2/18 1:38 PM, James Graham wrote: Experimental (i.e. nightly/dev) builds of Firefox and Chrome are run on Linux using Taskcluster after each commit to web-platform-tests. Would a commit to Firefox that fixes some tests and just touches wpt .ini

Multi-browser web-platform-tests results dashboard

https://wpt.fyi is a dashboard containing the results of the full web-platform-tests suite in multiple versions of current browsers. The default view shows test results in the latest stable releases of desktop Firefox/Chrome/Edge/Safari. There are several alternative views that are likely to b

Re: PSA: wpt MANIFEST.json has moved out of tree

On 24/09/2018 13:43, James Graham wrote: If you notice regressions from this change, please file a bug in the Testing::web-platform-tests component and needinfo me. Due to bug 1493674 we were mistakenly looking for test metadata in the objdir rather than the source dir. If you notice that

Re: PSA: wpt MANIFEST.json has moved out of tree

On 24/09/2018 14:01, Boris Zbarsky wrote: On 9/24/18 8:43 AM, James Graham wrote: Thanks to great work by Outreachy intern Ahilya Sinha (:Cactusmachete) [1], the in-tree wpt MANIFEST.json files are no longer used and will soon be removed. That's great news.  :) Invoking `mach wpt`

PSA: wpt MANIFEST.json has moved out of tree

Thanks to great work by Outreachy intern Ahilya Sinha (:Cactusmachete) [1], the in-tree wpt MANIFEST.json files are no longer used and will soon be removed. Invoking `mach wpt` will now cause a recent wpt manifest to be downloaded from Taskcluster into the objdir (if not already present) and

Re: Intent to Implement: Storage Access API

On 07/09/2018 21:27, Ehsan Akhgari wrote: Very cool, I did not know this!  It seems like test_driver.bless() is what we need here for simulating a user activation gesture. However it sounds like in this case you may need to add test-only APIs for manipulating internal browser state. Th

Re: Intent to Implement: Storage Access API

web-platform-tests: Our implementation unfortunately doesn’t come with web-platform-tests, for two reasons. One is that there is currently no way to mock user gestures in web platform tests [4], and the second reason is that furthermore, our implementation also depends on being able to manipulate

Re: ./mach try fuzzy: A Try Syntax Alternative

On 06/08/2018 01:25, Botond Ballo wrote: Is there an easy way to do a T-push (builds on all platforms, tests on one platform only) with |mach try fuzzy|? I usually do T-pushes using try syntax, by Trychooser seems to be out of date when it comes to building a T-push syntax for Android, so I'm at

Re: Developer Outreach - Web Platform Research and Recommendations

On 31/07/18 10:34, James Graham wrote: One of the underlying concerns I have here is that there are a lot of separate groups working on different parts of this. As one of the people involved, I would nevertheless struggle to articulate the overall Mozilla strategy to ensure that the web

Re: Developer Outreach - Web Platform Research and Recommendations

On 27/07/2018 21:26, Dietrich Ayala wrote: Additionally, much of what we're proposing is based directly on the interviews we had with people in different roles in the development of the web platform. Common themes were: lack of data for making selection/prioritization decisions, visibility of wha

Re: Proposed W3C Charters: Accessibility (APA and ARIA Working Groups)

A final clarification: On Fri, Jul 27, 2018 at 4:36 PM, Tantek Çelik wrote: > Even if we (Mozilla) are delayed with implementation, we can > still champion this stuff. We can still nominate someone to > participate in the WG with subject matter expertise to help guide what > we think will be mor

Re: Proposed W3C Charters: Accessibility (APA and ARIA Working Groups)

TL;DR: Thanks for the further explanation/clarification. I (reluctantly) agree that these concerns make sense and have nothing else to add as far as the response goes. On Fri, Jul 27, 2018 at 2:33 PM, Tantek Çelik wrote: > > The only thing worth > > noting is that while you say there's no need t

Re: Proposed W3C Charters: Accessibility (APA and ARIA Working Groups)

ception, while at the same time not resourcing accessibility sufficiently to make any reasonable progress at all. I'm not sure we can have it "both ways". Jamie On Fri, Jul 27, 2018 at 11:27 AM, Tantek Çelik wrote: > On Thu, Jul 26, 2018 at 6:04 PM, James Teh wrote: > &g

Re: Proposed W3C Charters: Accessibility (APA and ARIA Working Groups)

On Fri, Jul 27, 2018 at 2:09 AM, L. David Baron wrote: > So some comments on the ARIA charter at > https://www.w3.org/2018/03/draft-aria-charter : > ... > I guess it seems OK to have only one implementation > if there's really only going to be one implementation on that > platform... but allowing

Re: Developer Outreach - Web Platform Research and Recommendations

On 26/07/2018 19:15, Dietrich Ayala wrote: Why are we doing this? The goals of this effort are to ensure that the web platform technologies we're investing in are meeting the highest priority needs of today's designers and developers, and to accelerate availability and maximize adoption of th

Re: PSA: Re-run old (non-syntax) try pushes with |mach try again|

On 17/07/2018 21:16, Nicholas Alexander wrote: Ahal, On Tue, Jul 17, 2018 at 11:55 AM, Andrew Halberstadt > wrote: While |mach try fuzzy| is generally a better experience than try syntax, there are a few cases where it can be annoying. One common case was w

Re: Proposed W3C Charters: Accessibility (APA and ARIA Working Groups)

I (and others in the accessibility team) think we should support these charters. The ARIA working group is especially important in the future evolution of web accessibility. I have some potential concerns/questions regarding the personalisation semantics specifications from APA, but they're more sp

Re: Intent to ship: Changes to how offset*, client*, scroll* behave on tables

On 10/07/2018 17:25, Boris Zbarsky wrote: Bug: https://bugzilla.mozilla.org/show_bug.cgi?id=820891 Summary: In other browsers, and arguably per spec as far as cssom-view specs things, various geometry APIs on tables should report values for the table wrapper, not the table itself, because they

Re: PSA: pay attention when setting multiple reviewers in Phabricator

On 05/07/2018 18:19, Mark Côté wrote: I sympathize with the concerns here; however, changing the default would be a very invasive change to Phabricator, which would not only be complex to implement but troublesome to maintain, as we upgrade Phabricator every week or two. This is, however, som

Re: Fwd: WPT Developer Survey - June 2018

On 19/06/2018 10:01, Andreas Tolfsen wrote: If you run, write, or work with Web Platform Tests (WPT) in some capacity, we would like to invite you to answer a short survey. The survey helps us identify ergonomic problems so that we can improve the tools for building an interoperable web platform

Re: Launch of Phabricator and Lando for mozilla-central

On 06/06/2018 15:57, Mark Côté wrote: Similarly, there are two other features which are not part of initial launch but will follow in subsequent releases: * Stacked revisions. If you have a stack of revisions, that is, two or more revisions with parent-child relationships, Lando cannot land th

Re: Intent to ship: media-capabilities

On 14/05/2018 16:19, Jean-Yves Avenard wrote: Media Capabilities allow for web sites to better determine what content to serve to the end user. Currently a media element offers the canPlayType method (https://html.spec.whatwg.org/multipage/media.html#dom-navigator-canplaytype-dev

Re: Intent to ship: PerformanceServerTiming

On 24/04/2018 22:36, Valentin Gosu wrote: On 24 April 2018 at 22:44, James Graham <https://bugs.chromium.org/p/chromium/issues/detail?id=702760> This affects web-compat, since per our "restrict new features to secure origins policy" the server

Re: Intent to ship: PerformanceServerTiming

On 24/04/2018 20:32, Valentin Gosu wrote: Bug 1423495 is set to land on m-c and we intend to let it ride the release train, meaning we are targeting Firefox 61. Chromium bug: https://bugs.chromium.org/p/chromium/issues/detail?id=702760 This

Re: Intent To Require Manifests For Vendored Code In mozilla-central

On 10/04/2018 14:34, Ted Mielczarek wrote: On Tue, Apr 10, 2018, at 9:23 AM, James Graham wrote: On 10/04/2018 05:25, glob wrote: mozilla-central contains code vendored from external sources. Currently there is no standard way to document and update this code. In order to facilitate automation

Re: Intent To Require Manifests For Vendored Code In mozilla-central

On 10/04/2018 05:25, glob wrote: mozilla-central contains code vendored from external sources. Currently there is no standard way to document and update this code. In order to facilitate automation around auditing, vendoring, and linting we intend to require all vendored code to be annotated wi

Re: Intent to ship: OpenType Variation Font support

On 19/03/2018 22:32, Jonathan Kew wrote: As of this week, for the mozilla-61 cycle, I plan to turn support for OpenType Font Variations on by default. It has been developed behind the layout.css.font-variations.enabled and gfx.downloadable_fonts.keep_variation_tables preferences. Other UAs s

Re: Intent to ship: Module scripts (ES6 modules)

On 14/02/2018 14:13, jcoppe...@mozilla.com wrote: I intend to turn on

Re: Improved wpt-sync now running experimentally

On 12/02/2018 20:08, smaug wrote: On 02/09/2018 10:39 PM, James Graham wrote: On 09/02/2018 19:59, Josh Bowman-Matthews wrote: On 2/9/18 1:26 PM, James Graham wrote: * One bug per PR we downstream, filed in a component determined by the files changed in the PR. What does this mean exactly

Re: Improved wpt-sync now running experimentally

On 09/02/2018 19:59, Josh Bowman-Matthews wrote: On 2/9/18 1:26 PM, James Graham wrote: * One bug per PR we downstream, filed in a component determined by the files changed in the PR. What does this mean exactly? What is the desired outcome of these bugs? They're tracking the proces

Improved wpt-sync now running experimentally

The new sync for web-platform-tests is now running experimentally. This provides two way sync between the w3c/web-platform-tests repository on GitHub and mozilla-central, so allowing gecko developers to contribute to web-platform-tests using their normal gecko workflow, and ensuring that we get

  1   2   3   >