immersive-web dom-overlays issues

immersive-web / dom-overlays

A feature incubation repo for layering DOM content on/in WebXR content. Feature lead: Piotr Bialecki

https://immersive-web.github.io/dom-overlays/

Other

70 stars 9 forks source link

issues

Newest

Newest Most commented Recently updated Oldest Least commented Least recently updated

Give :xr-overlay a definition type

#56 tabatkins closed 2 months ago
1
domOverlay in AR

#55 wildy13 opened 3 months ago
0
Updating editor (klausw => bialpio)

#53 klausw closed 2 years ago
0
Align with DOM suggested phrasing when firing an event

#52 dontcallmedom closed 2 years ago
0
added skelton-ish changes section

#51 himorin closed 2 years ago
0
fixed link errors

#50 himorin closed 2 years ago
1
Added a link to list_spec in README

#49 himorin closed 2 years ago
0
replaced github actions with streamline publication

#48 himorin closed 2 years ago
2
fixed links in header

#47 himorin closed 2 years ago
2
Update the abstract

#46 klausw closed 3 years ago
1
added favicons

#45 himorin opened 3 years ago
0
added TR for bikeshed

#44 himorin opened 3 years ago
0
Use cases for DOM Overlays in VR

#42 AdaRoseCannon opened 3 years ago
31
XRDOMOverlayState should be an interface

#41 foolip opened 3 years ago
0
Updates based on TAG feedback

#40 klausw closed 3 years ago
0
updated TravisCI

#39 himorin closed 3 years ago
0
Explain optional/required and presence check

#38 klausw closed 3 years ago
0
Refactor explainer

#37 klausw closed 3 years ago
0
CSS Backdrop FIlter Behaviour

#36 AdaRoseCannon closed 4 years ago
2
Feature 'dom-overlay' is not supported for mode: immersive-vr

#35 ivnnv closed 4 years ago
4
Updated readme to follow WG repos

#34 himorin closed 4 years ago
2
`beforexrselect` confusion

#33 alice closed 3 years ago
1
Accessibility out of scope?

#32 alice closed 3 years ago
2
added w3c.json and metadata to WG/ED

#31 himorin closed 4 years ago
1
Specify -Z axis for target ray intersection

#30 Manishearth closed 4 years ago
1
Spec forces a choice of pointing ray

#29 Manishearth opened 4 years ago
0
Rethink non-goals: placing DOM elements in the 3D scene

#28 haywirez closed 3 years ago
9
Consider calling out XFO and `frame-ancestors` in addition to `frame-src`.

#27 mikewest opened 4 years ago
0
Overide css for overlaid element

#26 devsheder closed 4 years ago
7
Add self-contained barebones example and screenshot

#25 klausw closed 4 years ago
0
Use portrait mode image for explainer

#24 klausw closed 4 years ago
0
Explainer clarifications and image

#23 klausw closed 4 years ago
0
Clarifications and requirements for non-root paint/stacking

#22 klausw closed 4 years ago
0
Cross origin content and input

#21 RafaelCintron opened 4 years ago
0
DOM overlay not well-defined for non-roots

#20 chrishtr closed 4 years ago
9
Add UA option to hide the entire page on other displays

#19 klausw closed 4 years ago
0
Clarification on domOverlay element and sizing

#18 RafaelCintron closed 4 years ago
8
Add explanations for non-Fullscreen-API semantics and use case

#17 klausw closed 4 years ago
1
Interoperability and compatibility - browser vendors & web developers support for DOM Overlay

#16 klausw opened 4 years ago
1
Spell out how optional Fullscreen API integration works

#15 foolip opened 4 years ago
6
CSS pseudo-class/styling and Fullscreen API integration

#14 klausw closed 4 years ago
3
Update explainer to match latest spec

#13 klausw closed 4 years ago
0
Add DOM Overlay test to WPT

#12 klausw closed 4 years ago
1
Add security/privacy questionnaire

#11 klausw closed 4 years ago
0
Add "head-locked" type and clarifying note

#10 klausw closed 4 years ago
4
At what distance should this overlay be placed w/ Head Mounted MR devices

#9 raviramachandra closed 4 years ago
10
Request for Examples

#8 raviramachandra closed 4 years ago
4
Draft DOM Overlay spec for discussion

#7 klausw closed 4 years ago
10
Decide on the feature name

#6 klausw closed 4 years ago
3
Configuring the active DOM element for the overlay

#5 klausw closed 4 years ago
6