According to the spec, the Navigation Type enums should all begin with TYPE_. Ours don't.
Also, TYPE_RESERVED is missing.
Created attachment 76821 [details] Patch
LGTM I have a weak preference that we get don't add TYPE_RESERVED. I just don't think it provides any real value. But it may or may not be worth changing the spec at this point and we should pass the compliance tests.
(In reply to comment #3) > LGTM > > I have a weak preference that we get don't add TYPE_RESERVED. I just don't think it provides any real value. But it may or may not be worth changing the spec at this point and we should pass the compliance tests. Agreed. They're really rushing to get this to last call and I don't think this is worth holding them up. Can I get an r+ from a reviewer?
The commit-queue encountered the following flaky tests while processing attachment 76821 [details]: inspector/styles-new-API.html bug 50889 (authors: apavlov@chromium.org and pfeldman@chromium.org) http/tests/inspector/extensions-headers.html bug 51239 (author: caseq@chromium.org) The commit-queue is continuing to process your patch.
Comment on attachment 76821 [details] Patch Clearing flags on attachment: 76821 Committed r74241: <http://trac.webkit.org/changeset/74241>
All reviewed patches have been landed. Closing bug.