You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The "Also in" section in the list of Methods in the API Documentation as seen below can be a usability error. It is not clear that they are links due to being grey and not blue, they have no underline even when you hover on them, and it isn't clear where one link ends and another begins (for example Manipulate and Class Attribute are separate links even though the share the same "button" or border.
The text was updated successfully, but these errors were encountered:
For my college assignment I had to read about functional bugs vs usability bugs and then make my own bug report. This case is just a simple usability bug and my course would most likely state that the "Also in:" section just needs to be a little more clear that it is clickable. My ideas would be to make the words blue (as that is the "standard" for links), make them underlined or changed when hovered, and/or make each individual link have it's own box/border so users know that links such as "Manipulation" and "Class Attribute" are separate links and not multiple (this could also be done by having an underline appear under the specific link you hover over).
I don't necessarily feel qualified for these suggestions to actually be implemented and my goal was to just try a "bug report" that my assignment required. I couldn't really find any so I found just a small confusing example to use. Do not feel the need to take my bug report or suggestions into serious considerations considering you are most likely more qualified and experienced than I am.
(I am doing this for a College Assignment)
The "Also in" section in the list of Methods in the API Documentation as seen below can be a usability error. It is not clear that they are links due to being grey and not blue, they have no underline even when you hover on them, and it isn't clear where one link ends and another begins (for example Manipulate and Class Attribute are separate links even though the share the same "button" or border.
The text was updated successfully, but these errors were encountered: