The goal of this project is to provide the necessary support for subcompositor to enable naviframe with external process. There is a separate task for handling the API of the new naviframe.
Is there any plan for this work ?
I want to know whether details of this work were discussed.
This seems like view-managing would be done by window manager side ... am I right ?
Please share any news on this task :)
hmm. need to re-open this. a nested compositor is not really what is needed. xdg-foreign is what is really needed. this is security sensitve. imagine this involved oath. i want to have my app get an auth token AND have it approved. so as part of this somone/thing runs the browser (in a secure env its run not as a child process but via a launcher daemon with another smack label)... and the browser goes to a page and asks me to log in or approve the access. now the first app can steal (keylog) my password if it is done as a nested compositor.
in some situations a nested compositor is fine. in others like the above it's not. the window stack is really all about the 2nd case. where you may have windows of your own OR windows from some other process/client that are part of your "dialog stack" or series of frames. you do not want to leak things like passwords or have the ability to just auto "clikc ok" for the user when the point is to have the user himself approve the access.
while a nested compositor is cool and neat for some uses, it's not for this.