Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / w3c/window-management issues and pull requests
#70 - Define the multi-screen origin
Pull Request -
State: closed - Opened by quisquous almost 3 years ago
- 2 comments
#69 - Update explainer and spec for API renaming/removals
Pull Request -
State: closed - Opened by quisquous almost 3 years ago
- 2 comments
#69 - Update explainer and spec for API renaming/removals
Pull Request -
State: closed - Opened by quisquous almost 3 years ago
- 2 comments
#67 - Collecting Developer Feedback
Issue -
State: open - Opened by michaelwasserman almost 3 years ago
- 5 comments
Labels: question
#65 - Provide Physical Dimensions / PPI of Displays
Issue -
State: open - Opened by seflless about 3 years ago
- 9 comments
Labels: enhancement
#64 - Spec: Define the multi-screen origin, clarify primary screen origin definition
Issue -
State: closed - Opened by michaelwasserman about 3 years ago
- 1 comment
Labels: documentation
#64 - Spec: Define the multi-screen origin, clarify primary screen origin definition
Issue -
State: closed - Opened by michaelwasserman about 3 years ago
- 1 comment
Labels: documentation
#54 - bikeshed: consider naming the permission multiscreen instead of window-placement
Issue -
State: closed - Opened by quisquous over 3 years ago
- 3 comments
Labels: question
#52 - ScreensAdvanced.isExtended mixes system-level concepts with individual screen attributes
Issue -
State: closed - Opened by quisquous over 3 years ago
- 5 comments
Labels: question
#52 - ScreensAdvanced.isExtended mixes system-level concepts with individual screen attributes
Issue -
State: closed - Opened by quisquous over 3 years ago
- 5 comments
Labels: question
#50 - bikeshed: window.getScreens().screens is an odd naming pattern
Issue -
State: closed - Opened by quisquous over 3 years ago
- 4 comments
Labels: bug, documentation
#50 - bikeshed: window.getScreens().screens is an odd naming pattern
Issue -
State: closed - Opened by quisquous over 3 years ago
- 4 comments
Labels: bug, documentation
#49 - Should screens.currentScreen be [SameObject] ?
Issue -
State: closed - Opened by inexorabletash over 3 years ago
- 6 comments
Labels: question
#48 - Feature-parity with `app.window.create(..., { frame: 'none' })` available in Chrome Apps platform
Issue -
State: open - Opened by exikyut over 3 years ago
- 2 comments
Labels: enhancement
#47 - Exposing the refresh rate of displays
Issue -
State: open - Opened by jespertheend over 3 years ago
- 5 comments
Labels: enhancement
#46 - Can I test the API using local files?
Issue -
State: closed - Opened by jjeff almost 4 years ago
- 6 comments
#46 - Can I test the API using local files?
Issue -
State: closed - Opened by jjeff almost 4 years ago
- 6 comments
#44 - Support for window placement on dual-screen or foldable devices?
Issue -
State: closed - Opened by michaelwasserman almost 4 years ago
- 1 comment
Labels: enhancement, question
#42 - colorDepth and pixelDepth
Issue -
State: closed - Opened by fantasai almost 4 years ago
- 2 comments
Labels: question, wontfix
#41 - Align terminology across related specs
Issue -
State: open - Opened by anssiko almost 4 years ago
- 1 comment
Labels: documentation
#41 - Align terminology across related specs
Issue -
State: open - Opened by anssiko almost 4 years ago
- 1 comment
Labels: documentation
#38 - Explore window-reuse nuances of cross-screen fullscreen
Issue -
State: open - Opened by michaelwasserman almost 4 years ago
- 1 comment
Labels: enhancement, question
#38 - Explore window-reuse nuances of cross-screen fullscreen
Issue -
State: open - Opened by michaelwasserman almost 4 years ago
- 1 comment
Labels: enhancement, question
#35 - Integrate with Window Segmentation API
Issue -
State: closed - Opened by kenchris about 4 years ago
- 5 comments
Labels: documentation, enhancement, question
#35 - Integrate with Window Segmentation API
Issue -
State: closed - Opened by kenchris about 4 years ago
- 5 comments
Labels: documentation, enhancement, question
#28 - Should `onscreenschange` provide useful data?
Issue -
State: open - Opened by tomayac about 4 years ago
- 6 comments
Labels: enhancement, question
#28 - Should `onscreenschange` provide useful data?
Issue -
State: open - Opened by tomayac about 4 years ago
- 6 comments
Labels: enhancement, question
#20 - HDR / WCG
Issue -
State: open - Opened by jimbankoski over 4 years ago
- 12 comments
Labels: enhancement
#19 - Specify the order of returned screen objects
Issue -
State: closed - Opened by michaelwasserman over 4 years ago
- 4 comments
Labels: bug, documentation
#18 - Reuse existing Screen interface or add something new?
Issue -
State: closed - Opened by michaelwasserman over 4 years ago
- 4 comments
Labels: question
#18 - Reuse existing Screen interface or add something new?
Issue -
State: closed - Opened by michaelwasserman over 4 years ago
- 4 comments
Labels: question
#17 - Request to track the "active" screen
Issue -
State: closed - Opened by michaelwasserman about 4 years ago
- 2 comments
Labels: enhancement
#12 - screenschange is easy to mistake for screenchange
Issue -
State: closed - Opened by kenchris over 4 years ago
- 3 comments
Labels: wontfix
#9 - Feature detection support?
Issue -
State: open - Opened by michaelwasserman over 4 years ago
- 3 comments
Labels: documentation, question
#7 - window.open should support the 'fullscreen' option
Issue -
State: open - Opened by cterefinko almost 5 years ago
- 7 comments
Labels: enhancement
#5 - Interactions of fullscreen windows while moving between displays
Issue -
State: open - Opened by cterefinko almost 5 years ago
- 1 comment
Labels: documentation
#3 - allow window minimize & restore (focus)
Issue -
State: open - Opened by nadavsinai about 5 years ago
- 10 comments
Labels: enhancement