What is reasoning behind making expand clickable area so tiny?

42 views
Skip to first unread message

Phill Hodgkinson

unread,
Nov 21, 2013, 11:21:48 AM11/21/13
to umbra...@googlegroups.com
Hi there,

I've noticed this previously and it's still there in the final release. I'm wondering what the reasoning is in forcing a user to click on the tiny arrow to expand a node (i.e. document types or content tree items). I continually click on the text, the entire row highlights when you mouse over it so it implies that it's clickable, and yet nothing happens. To me this is both counter intuitive and also difficult in that the tiny arrow is harder to click, both with a mouse and in touch interfaces. Why wouldn't the whole row be clickable? I don't think you'd hear anyone complain if you made this change but I'm sure people would appreciate a larger area to click on.

That said, 7 has made some amazing improvements between RC and Final Release, well done all!

Regards,
Phill

Richard Barg

unread,
Nov 21, 2014, 5:46:39 PM11/21/14
to umbra...@googlegroups.com
This is off topic Phil, but we can help you w/the issue you raised in this comment in Nov. 2013. We have 55 sites in one Umbraco instance. We have modified the CSS so screen real estate is optimized and manageable. Will be happy to share.


"Phill Says:
01 Nov 13 @ 02:40 GMT+1

@Sebastiaan and @Niels, thanks for the responses. Is there a forum thread specific to v7? I wouldn't mind giving some more (constructive) feedback but this doesn't seem the right place for it. But while I have your attention.... haha i.e. another issue I have with new UI is the vertical spacing/padding between elements. On a documents Properties tab I used to be able to see/edit all properties plus custom properties at once. Now on my 1440x900 monitor I have to scroll to be able to see even just the defaults, adding unnecessary "clicks" or "steps". I personally don't see the need for so much padding, especially not at the cost for forcing user to scroll. Anyway, if there's a forum you could point me to for voicing these types of things that would be great. They're obviously not "bugs" but to me they're a step backwards in usability so I wouldn't mind at least sharing my opinion."
Reply all
Reply to author
Forward
0 new messages