Initial Model element tests

[zachernuk]

A collection of semantic tests for the basic presence and web-platform functionality of the proposed HTML Model element, in development and discussion at
https://github.com/immersive-web/model-element/
and discussed with WHATWG here:
whatwg/html#10901
These tests are intended to accompany a PR to the WHATWG HTML specification to include HTMLModelElement as a new element, with further detail to be added upon TAG review and implementer updates.

As an initial pass, we aim to establish:

• HTMLModel as a distinct element
• The expected content model categories
• The relevant global attribute behaviors

This effort has support from WebKit, Meta Quest Browser and Samsung internet.

(cc @LaszloGombos, @cabanier, @marcoscaceres, @AdaRoseCannon)

[annevk]

Until the model element is part of the HTML standard should mark these tests as .tentative I think.

[cookiecrook]

Until the model element is part of the HTML standard should mark these tests as .tentative I think.

In case you haven't used this pattern before, Anne means the filenames in the PR should change from draggable.html to draggable.tentative.html for example. There are other patterns, like .optional for RFC-2119 MAY requirements.

[zachernuk]

Until the model element is part of the HTML standard should mark these tests as .tentative I think.

In case you haven't used this pattern before, Anne means the filenames in the PR should change from draggable.html to draggable.tentative.html for example. There are other patterns, like .optional for RFC-2119 MAY requirements.

That makes sense - is that correctly addressed here? 3e57b2e

[mkeblx]

Potential nit, a couple of the files end in .htm. I don't know if there is a functional reason for this.

% fd -e html | wc -l
   57946
% fd -e htm | wc -l 
     687

[mkeblx]

After a recent discussion it was likely decided to make model element require HTTPS:
immersive-web/model-element#109 (comment)

Thus files should have a https.html extension (https://web-platform-tests.org/writing-tests/general-guidelines.html#https)

[zachernuk]

Potential nit, a couple of the files end in .htm. I don't know if there is a functional reason for this.

% fd -e html | wc -l
   57946
% fd -e htm | wc -l 
     687

I had thought I was following an established pattern but think I had misread the situation, I've updated now.

[zachernuk]

After a recent discussion it was likely decided to make model element require HTTPS: immersive-web/model-element#109 (comment)

Thus files should have a https.html extension (https://web-platform-tests.org/writing-tests/general-guidelines.html#https)

I agree that it should - the only question I have here is whether those tests are about running in HTTPS rather than merely interacting with something that otherwise happens to be HTTPS-dependent.

The tests in question aren't even required to load content at this stage, and presumably the DOM-facing container needs to function even if the content-load fails. What do you think?

[mkeblx]

Got it. That makes sense to draw a distinction on tests that would require https, e.g. a successful load, etc. and reserve .https.html for those.