<!DOCTYPE html> <html> <head> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> </head> <body text="#000000" bgcolor="#FFFFFF"> Do you consider a Morph to be, by default, a widget or a shape? Another point, it should be implemented as a morph property, as it is done for other testing event methods. Consider my initial example with PluggableListOfMorph, the contents of the list are bordered box morph. I don't want to subclass it to set handlesKeyboardFocus to respond to my need, true or false. So an additional suggestion is Morph>>handlesKeyboardFocus ^ self hasProperty: #'handlesKeyboardFocus' Also, please add some comments to the method. What does it mean it handles keyboard focus? Is it to respond to TAB keyboard or something else? It is not clear to me. Thanks Hilaire <div class="moz-cite-prefix">Le 16/07/2026 à 07:44, Luciano Notarfrancesco via Cuis-dev a écrit : </div> <blockquote type="cite" cite="mid:CAL5GDyrCDhG1QWswyoHqOD2RLuq3T96=s5_OY4QBCg9kJz2fEQ@mail.gmail.com"> <div dir="ltr">I was thinking, perhaps Morph>>handlesKeyboardFocus should answer false so that morphs don't get focus by default unless you implement this method? Would that lead to more predictable behaviour? What's the advantage of the current behaviour? It just saves you from implementing handlesKeyboardFocus in your morphs or does it have any other advantage?</div> </blockquote> <pre class="moz-signature" cols="72">-- <a class="moz-txt-link-freetext" href="http://mamot.fr/@drgeo">http://mamot.fr/@drgeo</a></pre> </body> </html>