On Thu, Dec 14, 2017 at 2:31 PM Tantek Çelik wrote:
>
> There is one test row that is red for all implementations, digging into it.
>
> https://wpt.fyi/IndexedDB/idbobjectstore_createIndex15-autoincrement.htm
>
> It looks like there are problems with "Auto-Increment Primary Key",
> specifically:
small improvement of existing IndexedDB APIs wanted by web
developers and are shipped since FF51, so I agree to vote it as proposed
recommendation.
Thanks,
Bevis Tseng
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
On Fri, Dec 8, 2017 at 3:21 PM Bevis Tseng wrote:
> After Bug 1193394 <https://bugzilla.mozilla.org/show_bug.cgi?id=1193394>
> revealed the problem about how Firefox performs microtasks differently from
> what has be specified in HTML standard,
>
A small correction here which
ld scheduling behavior.
Then, additional migration work is required to make it behave correctly in
both new/old scheduling to allow the main patch to be landed after all
these failure are fixed.
BTW, if you need face to face discussion during Austin All Hands, please
feel free to ping me on irc (:bev
On Thu, Apr 20, 2017 at 11:13 PM, Bevis Tseng wrote:
>
>
> On Thu, Apr 20, 2017 at 10:15 AM, Bevis Tseng wrote:
>
>> A soft reminder of using AbstractThread::GetCurrent()/MainThread()
>> after some design change for Quantum-DOM.
>>
>> If this message/ca
On Thu, Apr 20, 2017 at 10:15 AM, Bevis Tseng wrote:
> A soft reminder of using AbstractThread::GetCurrent()/MainThread()
> after some design change for Quantum-DOM.
>
> If this message/callback is to be handled on *the main thread of the
> content process*, please use the rep
DOM#AbstractThread::MainThread> instead.
If you're in background thread or not in content process, you are totally
fine to use AbstractThread::GetCurrent()/MainThread().
Regards,
Bevis Tseng
On Thu, Apr 20, 2017 at 2:54 AM, Kan-Ru Chen wrote:
> Hello!
>
> With bug 1313200 landed, as
On Sat, Apr 8, 2017 at 6:03 AM, Chris Peterson
wrote:
>
> Are the bugs to label runnables good for volunteer contributors? Or would
> it be fastest for a DOM expert or engineers from each module to rip through
> the open bugs? Do we need to ask module owners to prioritize these bugs? :)
>
> https
On Wed, Jul 22, 2015 at 11:06 PM, Jonas Sicking wrote:
> On Wed, Jul 22, 2015 at 3:38 AM, Bevis Tseng wrote:
> > To prevent exposing too much in the web api level unnecessarily,
> > instead of creating new attribute in Navigator.webidl,
> > we could define the ImsHandle
ity. Drop the moz/Moz prefixing though.
>
> (I don't have enough time to go through this immediately: my time over
> the next two weeks is highly constrained, so forgive me for not
> engaging in this thread to the extent that you might like.)
>
> On Tue, Jul 21, 2015 at 11:50
Hi all,
I am from RIL team in Mozilla Taipei.
I'm glad to propose you a new module/web api called "IMS Registration
Manager". It is worth sharing you the details and having suggestion
and feedback from you! :)
IMS(IP Multimedia Subsystem) is a new infrastructure and is very
important in mobi
11 matches
Mail list logo
