Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Expand and revise examples section #89

Open
wants to merge 18 commits into
base: main
Choose a base branch
from
Open

Expand and revise examples section #89

wants to merge 18 commits into from

Conversation

zachernuk
Copy link
Collaborator

@zachernuk zachernuk commented Jul 8, 2024

Added the examples already sketched out in the document and added some more based on a tentative approach to MVP functionality.


Preview | Diff

@zachernuk
Copy link
Collaborator Author

/agenda

@probot-label probot-label bot added the agenda To be discussed at a future CG meeting label Jul 8, 2024
index.html Outdated Show resolved Hide resolved
index.html Outdated Show resolved Hide resolved
index.html Outdated Show resolved Hide resolved
index.html Outdated Show resolved Hide resolved
index.html Outdated Show resolved Hide resolved
index.html Outdated Show resolved Hide resolved
zachernuk and others added 9 commits July 10, 2024 17:12
Co-authored-by: Marcos Cáceres <[email protected]>
Co-authored-by: Marcos Cáceres <[email protected]>
Co-authored-by: Marcos Cáceres <[email protected]>
Co-authored-by: Marcos Cáceres <[email protected]>
Co-authored-by: Marcos Cáceres <[email protected]>
Co-authored-by: Marcos Cáceres <[email protected]>
Co-authored-by: Marcos Cáceres <[email protected]>
…ion discussed rather than a single binary attribute
@zachernuk
Copy link
Collaborator Author

@DRx3D I've updated the attribute for providing orbit input from interactive to stagemode="orbit".
(there is also an established HTML attribute called inputmode but it seems to relate specifically to textual input, so it may be better to pick a different name)

@zachernuk
Copy link
Collaborator Author

@DRx3D After some investigation and discussion, it seems that a top-level src attribute overrides anything coming from a set of <source> elements within <video>. I think we should follow their lead and have updated to reflect that.

Loading and parsing
</h3>
<p>
A model element whose source path resolves to a valid resource
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure there's a lot of value to adding this example here because it's so limited (plus it doesn't really deal with "loading or parsing", just very simple error handling). Consider that, like any event handling element, the element will deal (in one way or another) with all these event handler attributes:
https://html.spec.whatwg.org/#event-handlers-on-elements,-document-objects,-and-window-objects

Also, if we end up treating these elements as akin to media elements, then we might end up using these error codes, etc.:
https://html.spec.whatwg.org/#error-codes

I'd be inclined to either rename this section "Error handling" or removing it entirely until we figure out if model is a media element.

index.html Outdated
<aside class="note">
The bounding box and sphere is often computed based on the visible object
hierarchy on the first animation frame (if an animation is present),
and according only to the geometry information directly specified.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: "specified" by who? (can we change this to active voice?)

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

updated to reflect that rendering contexts generally compute it this way - it may need to be called out as non-normative or otherwise an observation of the state of the art.

Processing model contents
</h3>
<p data-cite="infra geometry-1" >
A 3D asset file contains positional data for the surfaces and objects
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The text in this section feels more like spec text than an example (it's a bit uncommon to talk about how the internals work in an example)... I wonder if we should move this or actually simplify all this into an example of usage?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@marcoscaceres I think it's not example content at all, yeah - I'll pull it out of this PR. Is there a good section name / description of this kind of content you'd recommend instead?

index.html Outdated Show resolved Hide resolved
index.html Outdated Show resolved Hide resolved
index.html Outdated Show resolved Hide resolved
index.html Outdated
<pre class="html">

&lt;figure&gt;
&lt;model alt="A gray, ceramic teapot with an innovative spout" &gt;
Copy link
Contributor

@marcoscaceres marcoscaceres Jul 23, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I still think we should get rid of alt=... the html around it or inside the element provides way better and more accessible fallback content (eg., <figurecaption>).

@Yonet Yonet removed the agenda To be discussed at a future CG meeting label Aug 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants