How is this for the description of IA2_STATE_PINNED? Indicates that an object is temporarily fixed at a certain location. One example is a browser tab that when pinned cannot be moved until unpinned. Another example is a movable or floating object that when pinned remains in its pinned location until being unpinned.
David, Can a pinned FF tab be closed? I am assuming pinned doesn't imply anything about an object's delete-ability. BTW, TabMixPlus adds a "protected" context menu item for tabs. You can't close a tab in this state. Pete Pete Brunet wrote: > Thanks to David and Brian. I think "pinned" is the right word to use. > -- > *Pete Brunet* > > a11ysoft - Accessibility Architecture and Development > (512) 238-6967 (work), (512) 689-4155 (cell) > Skype: pete.brunet > IM: ptbrunet (AOL, Google), [email protected] (MSN) > http://www.a11ysoft.com/about/ > Ionosphere: WS4G > > Brian Cragun wrote: >> Pinned is widely used with "floating" menus or objects. Pinning the >> object keep it in one place and/or on the uppermost layer, where it >> is visible. People use pinning so they can keep the item visible for >> quick access or reference. We might take clues from the purpose and >> use of pinning. >> >> In a serial audio stream, pinning is a little more than persistance, >> it infers keeping it handy, available, easily findable, quick >> reference. Permanent is too strong, because you can "unpin" it. >> But temporarily permanent is accurate. >> >> Regards, >> >> Brian >> >> Brian Cragun >> IBM AbilityLab Consultant >> Human Ability & Accessibility Center >> www.ibm.com/able & w3.ibm.com/able >> W:(720)-663-2801 H:(507)288-2437 >> >> >> >> >> From: Pete Brunet <[email protected]> >> To: IA2 List <[email protected]> >> Date: 11/30/2010 09:14 AM >> Subject: Re: [Accessibility-ia2] IA2_STATE_PINNED >> Sent by: [email protected] >> ------------------------------------------------------------------------ >> >> >> >> Is "pinned" a widely used GUI concept? It brings to mind something >> that is movable but currently fixed at a certain position, i.e. it >> conveys two concepts, neither of which seems to exactly fit the >> scenario given by David. It seems "permanent" (or "persistent") >> would be a better word. >> >> Pete >> >> James Teh wrote: >> On 19/11/2010 5:23 AM, David Bolter wrote: >> >> In Firefox 4 betas you can pin browser tabs. This means that the tab >> will become a permanent tab that is visually distinct and appears >> together with other pinned tabs to the left of the regular tabs. >> >> It's worth noting that this is not an application specific concept. It >> appears elsewhere (e.g. Windows 7 taskbar and Start menu) and will >> probably continue to appear in new applications as well. >> >> >> So, create an IA2_STATE_PINNED or expose an object attribute? >> >> My vote is for the state. This is a boolean state, so a state makes >> sense. In addition, having it as an object attribute when it could be a >> state suggests that it is an application specific hack, and is this >> case, it probably shouldn't be implemented as a boolean value at all. >> >> The practical problem with exposing it as a state is that we need a >> revision to the IA2 IDL, which may take time that Firefox 4 doesn't have. >> >> Jamie >> >> > > > ------------------------------------------------------------------------ > > _______________________________________________ > Accessibility-ia2 mailing list > [email protected] > https://lists.linux-foundation.org/mailman/listinfo/accessibility-ia2 >
_______________________________________________ Accessibility-ia2 mailing list [email protected] https://lists.linux-foundation.org/mailman/listinfo/accessibility-ia2
