Re:Wayland in Gnome: two progress reports
by wmf on Sunday August 24, 2014 @08:54PM
(#8220146)
It is odd, sandboxing just the graphics stack.
Since Wayland is a redesign of the graphics stack it looks like they decided to redesign it in a secure way rather than waiting for some system-wide security architecture to be designed. GNOME is working on full sandboxing: https://news.ycombinator.com/item?id=8219309
It sounds like something as simple as a keyboard macro manager would not be doable...
That's doable in the compositor/window manager.
I'd also hate to try and write UI test automation for Wayland apps.
Since Wayland is a redesign of the graphics stack it looks like they decided to redesign it in a secure way rather than waiting for some system-wide security architecture to be designed. GNOME is working on full sandboxing: https://news.ycombinator.com/item?id=8219309
It sounds like something as simple as a keyboard macro manager would not be doable...
That's doable in the compositor/window manager.
I'd also hate to try and write UI test automation for Wayland apps.
That's possible either through accessibility interfaces ( https://developer.gnome.org/accessibility-devel-guide/stable... ) or the compositor/window manager. Note that many OS X "haxies" also use the accessibility API.
Heck what about services that do browser test renders?
That should be no problem using either a modified browser or modified compositor.