Randell Jesup
Randell Jesup
**URL**: https://glassdoor.com **Browser / Version**: Firefox 104.0 **Operating System**: Linux **Tested Another Browser**: Yes Chrome **Problem type**: Site is not usable **Description**: Buttons or links not working **Steps to Reproduce**:...
The web-platform tests check (in a few instances) that async operations like truncate fail if there's another async operation still unresolved. a) there's nothing in the spec about this b)...
There's only a single line of normative definition for resolve() (which per other discussion here should be renamed). The non-normative language is fairly complete.
While the WPT tests appear to test a few things with deleted File/Directory handles (like that values() on a deleted directory returns NotFoundError), there's no spec text that I see...
WPT tests for messaging use queryPermission(); this isn't defined here. It's in https://wicg.github.io/file-system-access/#api-filesystemhandle-querypermission The OPFS tests shouldn't be using queryPermission, I believe
the webidl has `[[EnforceRange](https://webidl.spec.whatwg.org/#EnforceRange)] required [unsigned long long](https://webidl.spec.whatwg.org/#idl-unsigned-long-long) at;` However the WPT test of negative seek targets for SyncAccessHandles looks for dom NotSupportedError; the webidl spec says it should throw...
There are quite a few differences between the web-platform tests and the current spec -- which isn't really surprising, since the spec is still being modified. Some error conditions disagree,...
The language for getting FileHandles indicates you check the 'query access' for the file using readwrite if create is true, and read if create is false. (though it also says...
The WPT tests seem to assume you must pass 'at', and if you don't all reads start at 0. This is ... odd, especially for implementing the equivalent to read(),...
The text for truncate() on a WritableFileStream doesn't match the non-normative text, such as the discussion of the cursor position.