immersive-web / immersive-web/model-element

Presentation as a first-class DOM element

Open
#99 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
HTML
Stars
86
Forks
12
Avg merge
7h 12m
Merged PRs (30d)
1

Description

While most of the issues about HTMLModelElement relate what it's displaying (i.e. 3D rendered content, animated and then lit by some lighting environment), it's also important to consider how it's presented in the page, alongside other DOM elements. What are requirements that need to apply?

For example, while it's not "realistic" to be able to construct a blurred 3D model, alter its contrast or to apply grayscale or sepia toning, these are mainstays of DOM representation - both with direct filter CSS directives on an element's hierarchy, or based on backdrop-filter directives on anything on top. While it may seem niche to feature these filtering environments, it's a frequent issue on sites with paywalls (think nytimes.com) or sites with position:sticky elements leveraging backdrop-filter:blur() presentation (like apple.com)

Similarly, it's clear that a monoscopic (or un-tracked) presentation of a Model can accommodate a fully transparent background, it's not immediately clear that other DOM content should be visible "behind" a model, particularly when it's displayed as on the surface of a page rather than in the portal behind it.

/agenda

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the HTMLModelElement presentation requirements described in the issue, especially CSS filter, backdrop-filter, transparency, and visibility of surrounding DOM content. Define the expected behavior for model presentation in-page and portal contexts; done means the requirements are explicit enough to guide implementation.

Written by the indexing model from the issue text.

Assessment

Tech stack
css, html
Domain
frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.