Re: WM_NAME vs. _NET_WM_NAME
Thomas Lübking <[email protected]> Mon, 27 Oct 2014 12:25:25 +0100
| Newsgroups | gmane.comp.gnome.wm-spec |
|---|---|
| Message-ID | <CAAPqV4R3N0S-QettpsxqygSCp=DcqnUV5VDMFrOZh9ws-0PC0g@mail.gmail.com> |
--===============5623146208958517382== Content-Type: multipart/alternative; boundary=001a11c23d0479d9f8050665c98a --001a11c23d0479d9f8050665c98a Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable It's a netwm spec bug: _NET_WM_NAME _NET_WM_NAME, UTF8_STRING The Client SHOULD set this to the title of the window in UTF-8 encoding. If set, the Window Manager should use this in preference to WM_NAME. ------ "should"... So any netwm compliant WM "should" prefer _NET_WM_NAME. Qt read that as "we won't support pre-netwm stuff anymore, so we can dittch it", but that's "wrong" - a perfectly netwm compliant wm can entirely ignore _NET_WM_NAME m= ( hlwm *should* please prefer _NET_WM_NAME, but Qt has to set WM_NAME if interested in a caption - at least they can not point the spec as reason (they can however deny support for WMs deviating from the specs "suggestions") Sorry for gmail webclient, Thomas Am Montag, 27. Oktober 2014 schrieb Florian Bruhin : > * Martin Gr=C3=A4=C3=9Flin <[email protected] <javascript:;>> [2014-10-2= 7 10:26:14 > +0100]: > > > > > It seems the Qt toolkit only sets _NET_WM_NAME and doesn't set > WM_NAME > > > > > at all. Now that raises some questions: > > > > > > > > > > - Should a client also set WM_NAME when setting _NET_WM_NAME? Sur= e, > > > > > > > > > > it's a good idea for backwards-compatiblity, but is it warrante= d > to > > > > > open a bug against Qt? (I'd say yes, but I'd like to hear other > > > > > opinions). > > > > > > > > From my reading of the relevant section in ICCCM (4.1.2.1) there is > no > > > > indication that a client is supposed to set it. Given that it's > certainly > > > > not a bug on Qt's side. If a window manager has problems with it, > it's > > > > more because the window manager doesn't support EWMH. > > > > > > Okay. I'll still open a bug in Qt then since it seems to raise > > > problems in the wild - then it's up to them to decide whether it's > > > worth to fix it or not ;) > > > > Fair enough, though I think it's not the task of a toolkit to be > bug-to-bug > > compatible with each window manager ;-) > > Sure, but since it lead to problems in two applications already > (KeePass and herbstluftwm), and everything else (tm) seems to set > both, it still (IMHO) is Qt's job to do it the way it causes the least > friction everywhere else. Of course it'd be ideal if everything else > would support _NET_WM_NAME (and I'll open a bugreport against KeePass > as well), but that's simply not the case. > > But as said, that's left to the Qt people to decide then ;) > > > > > Shameless plug: as you are using Qt 5, consider using > KF5::WindowSystem > > > > which is a nice Qt 5 (only, no further KDE dependencies) library > > > > implementing EWMH, supporting fallback to ICCCM if needed. It's the > > > > library powering KWin and Plasma (e.g. taskmanager) and also used i= n > > > > LXQt. > > > > > > Probably not an option with PyQt, and also that's not really a > > > dependency I want to have just to set a window title :D > > > > ah that be more for the case of reading the window title. > > That part is in KeePass (a password manager which can autofill fields > in a browser it finds via the title), I just happened to get the bug > report because it works everywhere else :P > > Thanks again for your insights! > > Florian > > -- > http://www.the-compiler.org | [email protected] <javascript:;> > (Mail/XMPP) > GPG 0xFD55A072 | http://the-compiler.org/pubkey.asc > I love long mails! | http://email.is-not-s.ms/ > --001a11c23d0479d9f8050665c98a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable It's a netwm spec bug:<div><br></div><div><div class=3D"titlepage" styl= e=3D"font-family:'Droid Sans';font-size:medium"><h3 class=3D"title"= >_NET_WM_NAME</h3></div><pre class=3D"programlisting" style>_NET_WM_NAME, U= TF8_STRING </pre><p style=3D"font-family:'Droid Sans';font-size:medium">The Cl= ient SHOULD set this to the title of the window in UTF-8 encoding. If set, = the Window Manager should use this in preference to WM_NAME.</p><p style=3D= "font-family:'Droid Sans';font-size:medium">------</p><p style=3D"f= ont-family:'Droid Sans';font-size:medium">"should"...</p>= <p style=3D"font-family:'Droid Sans';font-size:medium">So any netwm= compliant WM "should" prefer _NET_WM_NAME. Qt read that as "= ;we won't support pre-netwm stuff anymore, so we can dittch it", b= ut that's "wrong" - a perfectly netwm compliant wm can entire= ly ignore _NET_WM_NAME m(</p><p style=3D"font-family:'Droid Sans';f= ont-size:medium">hlwm *should* please prefer _NET_WM_NAME, but Qt has to se= t WM_NAME if interested in a caption - at least they can not point the spec= as reason (they can however deny support for WMs deviating from the specs = "suggestions")</p><p style=3D"font-family:'Droid Sans';fo= nt-size:medium"><br></p><p style=3D"font-family:'Droid Sans';font-s= ize:medium">Sorry for gmail webclient,</p><p style=3D"font-family:'Droi= d Sans';font-size:medium">Thomas</p><br>Am Montag, 27. Oktober 2014 sch= rieb Florian Bruhin :<br><blockquote class=3D"gmail_quote" style=3D"margin:= 0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">* Martin Gr=C3=A4= =C3=9Flin <<a href=3D"javascript:;" onclick=3D"_e(event, 'cvml',= '[email protected]')">[email protected]</a>> [2014-10-27 10:2= 6:14 +0100]:<br> > > > > It seems the Qt toolkit only sets _NET_WM_NAME and does= n't set WM_NAME<br> > > > > at all. Now that raises some questions:<br> > > > ><br> > > > > - Should a client also set WM_NAME when setting _NET_WM= _NAME? Sure,<br> > > > ><br> > > > >=C2=A0 =C2=A0it's a good idea for backwards-compatib= lity, but is it warranted to<br> > > > >=C2=A0 =C2=A0open a bug against Qt? (I'd say yes, bu= t I'd like to hear other<br> > > > >=C2=A0 =C2=A0opinions).<br> > > ><br> > > > From my reading of the relevant section in ICCCM (4.1.2.1) t= here is no<br> > > > indication that a client is supposed to set it. Given that i= t's certainly<br> > > > not a bug on Qt's side. If a window manager has problems= with it, it's<br> > > > more because the window manager doesn't support EWMH.<br= > > ><br> > > Okay. I'll still open a bug in Qt then since it seems to rais= e<br> > > problems in the wild - then it's up to them to decide whether= it's<br> > > worth to fix it or not ;)<br> ><br> > Fair enough, though I think it's not the task of a toolkit to be b= ug-to-bug<br> > compatible with each window manager ;-)<br> <br> Sure, but since it lead to problems in two applications already<br> (KeePass and herbstluftwm), and everything else (tm) seems to set<br> both, it still (IMHO) is Qt's job to do it the way it causes the least<= br> friction everywhere else. Of course it'd be ideal if everything else<br= > would support _NET_WM_NAME (and I'll open a bugreport against KeePass<b= r> as well), but that's simply not the case.<br> <br> But as said, that's left to the Qt people to decide then ;)<br> <br> > > > Shameless plug: as you are using Qt 5, consider using KF5::W= indowSystem<br> > > > which is a nice Qt 5 (only, no further KDE dependencies) lib= rary<br> > > > implementing EWMH, supporting fallback to ICCCM if needed. I= t's the<br> > > > library powering KWin and Plasma (e.g. taskmanager) and also= used in<br> > > > LXQt.<br> > ><br> > > Probably not an option with PyQt, and also that's not really = a<br> > > dependency I want to have just to set a window title :D<br> ><br> > ah that be more for the case of reading the window title.<br> <br> That part is in KeePass (a password manager which can autofill fields<br> in a browser it finds via the title), I just happened to get the bug<br> report because it works everywhere else :P<br> <br> Thanks again for your insights!<br> <br> Florian<br> <br> --<br> <a href=3D"http://www.the-compiler.org" target=3D"_blank">http://www.the-co= mpiler.org</a> | <a href=3D"javascript:;" onclick=3D"_e(event, 'cvml= 9;, '[email protected]')">[email protected]</a> (Mail/XMPP)<br> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0GPG 0xFD55A072 | <a href=3D= "http://the-compiler.org/pubkey.asc" target=3D"_blank">http://the-compiler.= org/pubkey.asc</a><br> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0I love long mails! | <a href=3D"http://em= ail.is-not-s.ms/" target=3D"_blank">http://email.is-not-s.ms/</a><br> </blockquote></div> --001a11c23d0479d9f8050665c98a-- --===============5623146208958517382== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ wm-spec-list mailing list [email protected] https://mail.gnome.org/mailman/listinfo/wm-spec-list --===============5623146208958517382==--