Thanks Johann. I agree it is important that we try to fix tests that have
been disabled. I think the sheriffs usually needinfo the triage owner
before/when disabling a test; I'm disappointed to hear that isn't happening
consistently.
However, I'd prefer not to change the review process for the dis
On 2020/01/09 3:35, James Graham wrote:
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.
In bug 1565170 I plan to disable the toSource methods that exists for
most objects in Firefox as well as the uneval method on the global
object. This change will affect all websites and WebExtension. Both
methods will still be available to Firefox internal (chrome) code, but
I plan on removing thos
On 1/8/20 12:50 PM, Geoffrey Brown wrote:
Instead of changing the reviewers, how about:
- we remind the sheriffs to needinfo
- #intermittent-reviewers check that needinfo is in place when
reviewing disabling patches.
To try and help address the visibility issue, we could also make
searchfox
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
Are people interested in a session(s) at the All-Hands on Searchfox? If
you're interested in any of the following things, please email me here
or at as...@mozilla.com or let me know via other channels, and let me
know which of the following you'd be interested in. My goal is to get a
rough co
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
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
The W3C is proposing a revised charter for:
Audio Working Group
https://www.w3.org/2011/audio/charter/audio-2019-ac.html
https://lists.w3.org/Archives/Public/public-new-work/2019Dec/0012.html
The differences from the previous charter are:
https://services.w3.org/htmldiff?doc1=https%3A%2F%2F
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.
I think the problem is making sure that items are triaged and placed into
peoples workflow sooner would solve this problem but I also ap
10 matches
Mail list logo
