[Webkit-unassigned] [Bug 157600] Modern IDB: IDB object constructors aren't exposed on the WorkerGlobalScope
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Wed May 11 21:05:20 PDT 2016
https://bugs.webkit.org/show_bug.cgi?id=157600
--- Comment #6 from Brady Eidson <beidson at apple.com> ---
(In reply to comment #5)
> (In reply to comment #4)
> > (In reply to comment #2)
> > > What is not working exactly?
> >
> > Sorry this wasn't mentioned - most of
> > http://w3c-test.org/IndexedDB/interfaces.worker is failing.
>
> I see now. Even though they are failing, I do not believe the reason they
> are failing is that the constructors are not exposed.
>
> They do:
> assert_own_property(self, this.name, "self does not have own property " +
> format_value(this.name));
>
> I assume this.name is the name of the property they want to check.
>
> This ends up calling:
> function _assert_own_property(name) {
> return function(object, property_name, description)
> {
> assert(object.hasOwnProperty(property_name),
> name, description,
> "expected property ${p} missing", {p:property_name});
> };
> }
>
> And we get a JS error saying that 'object' is undefined.
>
> AFAICT, 'object' is self since this is what we call assert_own_property()
> with as 1st parameter. Still trying to figure out what this means though.
Thanks for looking into it. I obviously misunderstood the issue, partially because the way that page is constructed is somewhat opaque. =/
--
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.webkit.org/pipermail/webkit-unassigned/attachments/20160512/97654bcd/attachment.html>
More information about the webkit-unassigned
mailing list