issues
search
w3c
/
window-management
Window Management API
https://www.w3.org/TR/window-management/
Other
95
stars
25
forks
source link
issues
Newest
Newest
Most commented
Recently updated
Oldest
Least commented
Least recently updated
Support for programmatically set of the permission: add a specific command line argument?
#96
matteotrapani
closed
2 years ago
5
Adjust boilerplate texts for migration to WG
#95
tidoust
closed
2 years ago
0
Are moveTo and resizeTo meant to be clamped to individual screens
#94
jpambrun
closed
2 years ago
1
Transfer GH repo to stage for First Public Working Draft
#93
anssiko
closed
2 years ago
5
Feature request: Fullscreen support on multiple screens
#92
shizukanaqun
opened
2 years ago
5
Specify behavior for browsers that do not want to reveal screen plurality via `Screen.isExtended`
#91
michaelwasserman
opened
2 years ago
0
Is ScreenDetails supposed to inherit from EventTarget?
#90
RByers
closed
2 years ago
1
Add "window-placement" to Powerful Features Registry (rather than Permissions)
#89
miketaylr
opened
2 years ago
1
Refine event firing steps
#88
michaelwasserman
closed
2 years ago
0
Refine spec concepts, terminology, prose, definitions, and algorithms.
#87
michaelwasserman
closed
2 years ago
1
Remove one more instance of `id`
#86
tomayac
closed
2 years ago
1
Add a basic HOWTO.md
#85
michaelwasserman
closed
2 years ago
0
Exposing content area coordinates
#84
michaelwasserman
opened
2 years ago
6
Fix spec language around "main dimension" and "secondary dimension".
#83
michaelwasserman
closed
2 years ago
1
Fix the multi-screen origin image; embed svg and add psd source to repo.
#82
michaelwasserman
closed
2 years ago
0
ScreenDetails defines "currentScreens" getter steps
#81
reillyeon
opened
2 years ago
4
Does window.getScreenDetails() always resolve with the same object?
#80
reillyeon
closed
2 years ago
4
Define a task source for completing asynchronous events
#79
reillyeon
closed
2 years ago
1
Fix typo in description of internal screens
#78
reillyeon
closed
2 years ago
0
Incorrect screen positions in "Virtual screen area" diagram
#77
reillyeon
closed
2 years ago
1
Fix the computation of window coordinates for a target screen
#76
michaelwasserman
closed
2 years ago
0
Write a simple usage overview
#75
michaelwasserman
closed
2 years ago
2
Question about multi screen spanning
#74
konorti
opened
2 years ago
4
Add msw as a spec editor; expand introduction.
#73
michaelwasserman
closed
2 years ago
0
spec: sort screens by x, then y
#72
quisquous
closed
2 years ago
1
Clean up various bikeshed issues, remove a lingering id reference, and update permissions integration
#71
inexorabletash
closed
2 years ago
0
Define the multi-screen origin
#70
quisquous
closed
2 years ago
2
Update explainer and spec for API renaming/removals
#69
quisquous
closed
2 years ago
2
Support for window placement in Wayland
#68
michaelwasserman
opened
2 years ago
0
Collecting Developer Feedback
#67
michaelwasserman
opened
2 years ago
5
Fixes typo
#66
mootari
closed
2 years ago
0
Provide Physical Dimensions / PPI of Displays
#65
seflless
opened
2 years ago
9
Spec: Define the multi-screen origin, clarify primary screen origin definition
#64
michaelwasserman
closed
2 years ago
1
Update pointers to link capturing APIs.
#63
evanstade
closed
2 years ago
0
Add quick reference to Window Placement.
#62
jpmedley
closed
2 years ago
6
Update index.bs syntax for a {{Window}} mention
#61
michaelwasserman
closed
2 years ago
0
Use auto-publish workflow to build spec.
#60
inexorabletash
closed
2 years ago
0
Update explainer and changes with permission policy
#59
quisquous
closed
2 years ago
2
Update explainer to reflect new events
#58
quisquous
closed
3 years ago
1
Spec link no longer works
#57
tomayac
closed
3 years ago
3
Rename default branch to 'main'
#56
inexorabletash
closed
3 years ago
2
Make currentScreen [SameObject], update onchange comment
#55
michaelwasserman
closed
3 years ago
0
bikeshed: consider naming the permission multiscreen instead of window-placement
#54
quisquous
closed
2 years ago
3
Update API to match the Explainer.
#53
inexorabletash
closed
3 years ago
2
ScreensAdvanced.isExtended mixes system-level concepts with individual screen attributes
#52
quisquous
closed
2 years ago
5
No easy way to listen to changes to all screen attributes
#51
quisquous
opened
3 years ago
1
bikeshed: window.getScreens().screens is an odd naming pattern
#50
quisquous
closed
2 years ago
4
Should screens.currentScreen be [SameObject] ?
#49
inexorabletash
closed
2 years ago
6
Feature-parity with `app.window.create(..., { frame: 'none' })` available in Chrome Apps platform
#48
exikyut
opened
3 years ago
2
Exposing the refresh rate of displays
#47
jespertheend
opened
3 years ago
5
Previous
Next