Op woensdag 2 oktober 2019 12:15:36 UTC+2 schreef Simon Giesecke:
> Hi,
>
> I recently [1] added STL-style iterators and begin/cbegin/end/cend
> member functions to nsBaseHashtable. This means that it is now
> possible to use range-based for and STL algorithms operating on
> iterators with all of
Hi everyone,
I plan to land a patch next week which will disable OriginAttribute
stripping in the permission manager. This will result in private browsing
windows and containers having isolated permissions. For example, if you
allow a website to send notifications in a normal window, this permissi
Putting on my hat as one of the people maintaining our permissions UI, I
generally agree with Henri that it would be nice to have a slightly
different UI for this use-case, i.e. as far as I can see the presented
origin does not in fact get access to the user's microphone and it's a bit
unclear what
Summary: The HTML Standard has for the longest time defined a feature
whereby you could exclusively use the h1 and sectioning elements, and
user agents would take care of adjusting the heading level according
to the nesting depth. Due to the complexity it never got adopted.
There’s an alternative p
Hi,
I am wondering if the following is supposed to be safe:
Given a function (from
https://searchfox.org/mozilla-central/source/dom/indexedDB/ActorsParent.cpp#9290):
nsAutoCString MakeColumnPairSelectionList(
const nsLiteralCString& aPlainColumnName,
const nsLiteralCString& aLocaleAwareC
On Thursday, May 23, 2019 at 4:34:14 AM UTC-4, Andrea Marchesini wrote:
> Link to the proposal:
> https://tools.ietf.org/html/draft-west-cookie-incrementalism-00
>
> Summary:
> "1. Treat the lack of an explicit "SameSite" attribute as
>"SameSite=Lax". That is, the "Set-Cookie" value "k
On 10/16/19 10:11 AM, Simon Giesecke wrote:
I am wondering if the following is supposed to be safe:
I would think so, yes. That said, using string types as return values
is not that common (using an outparam is the normal way they are used),
and so may be under-tested.
On the treeherder b
> On Sep 27, 2019, at 10:08 PM, Emilio Cobos Álvarez wrote:
>
> And, to be clear, we _can_ fix these compat issues, some way or another.
>
> One thought is to limit the amount of scroll adjustments without user
> scrolling or stuff like that, which would prevent the "you get stuck on the
> pa
Hi Emilio,
My recollection is that scroll anchoring was, in fact, a mess. I do not
personally have any opinion about whether scroll anchoring should be
removed from Gecko.
We (Chrome) decided to accept some compat issues for the sake of launching
the feature. This was a judgment call and could
On Fri, Sep 27, 2019 at 10:16 AM Emilio Cobos Álvarez
wrote:
> Hi Steve,
>
> On 9/27/19 4:03 PM, Steve Kobes wrote:
> > Hi Emilio,
> >
> > My recollection is that scroll anchoring was, in fact, a mess. I do not
> > personally have any opinion about whether scroll anchoring should be
> > removed
Hi,
When we initially started, we did have a rough time but I haven't seen any
issue nor heard any negative feedback about it. As far as I can tell from
the metrics, it seems to save a lot of user frustration.
Iirc, we collected a bunch of cases where the feature behave erratically.
We had a form
On Sun, Sep 29, 2019 at 2:24 PM Emilio Cobos Álvarez
wrote:
> pretty significant behavior differences were only
> caught later by me and people finding compat issues in the wild, like
> [3]. I was sad that the spec reflected absolutely nothing like what
> Blink implements. For this issue in part
I changed the subject of this thread to fit properly the current intent.
We also moved the FAQ from Gdocs to mozilla wiki [1] with more current and
updated info. I've also added more content about offline recognition and
how to use deep speech to the ones interested about it.
Let's just use the w
Hi all,
during the past year, while optimizing page load by changing how various tasks
within Gecko are scheduled,
intermittently failing tests have often caused trouble and required fixes to
them or occasionally
disabling them. Now with Fission we are seeing even more issues and we will do
pa
Sorry for the delay.
We agree that scroll anchoring has unrealized potential to be valuable for
the web at large, and to make that happen we should be investing a lot more
working with y'all (and if we can't succeed, probably removing it from
chromium). Concretely +Chris Harrelson who leads render
On Wed, Oct 16, 2019 at 4:40 AM Johann Hofmann wrote:
> as far as I can see the presented origin does not in fact get access to
> the user's microphone
The site doesn't get raw audio, but does get text representing what the
browser thinks it heard. It's the same kind of privacy risk as raw audi
I intend to enable CSS subgrid by default for v71.
*Summary: *
The CSS Grid 2 subgrid feature allows nested grids to participate in the
sizing of their parent's tracks, on a per-axis basis.
*Bug to turn on by default: *
https://bugzilla.mozilla.org/show_bug.cgi?id=1580894
*Meta bug where this
17 matches
Mail list logo
