Skip to content

Provide a hint where text is hidden behind a link in the overview #808

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
ghost opened this issue Aug 11, 2015 · 5 comments · Fixed by #809
Closed

Provide a hint where text is hidden behind a link in the overview #808

ghost opened this issue Aug 11, 2015 · 5 comments · Fixed by #809
Labels
P1 A high priority bug; for example, a single project is unusable or has many test failures type-enhancement A request for a change that isn't a bug
Milestone

Comments

@ghost
Copy link

ghost commented Aug 11, 2015

It should be more visible that clicking on a field/method in the class overview leads to more text.

I find it confusing is that when you look at a class like in

../dart-mirrors/MirrorsUsed-class.html

it is non-obvious that there is more text for a property if you click on it. Maybe we can add a little visual clue, like a 'more >>' or just three '...'?

@sethladd sethladd added this to the Branch milestone Aug 11, 2015
@sethladd sethladd modified the milestones: Branch, 0.5.0 Aug 11, 2015
@ghost ghost reopened this Aug 21, 2015
@ghost
Copy link
Author

ghost commented Aug 21, 2015

I don't think this has been fixed. I was asking for a visual clue that clicking on the property reveals documentation beyond the one-liner. So maybe adding an ellipsis that forwards to the full text after the one-liner.

@devoncarew
Copy link
Member

I think our fix wasn't sufficient; we show ellipses if the first paragraph of text runs over, but not if there's a 2nd paragraph (which is not shown in the summary).

@sethladd
Copy link
Contributor

Thanks for the report. We can definitely improve this.

@sethladd sethladd modified the milestones: 1.12, 0.5.0 Aug 21, 2015
@sethladd sethladd added the type-enhancement A request for a change that isn't a bug label Aug 21, 2015
@sethladd sethladd modified the milestones: 1.12, 0.6.0 Aug 21, 2015
@sethladd sethladd added the P1 A high priority bug; for example, a single project is unusable or has many test failures label Aug 21, 2015
@sethladd
Copy link
Contributor

We do this now:

screen shot 2015-08-21 at 3 54 45 pm

Is that sufficient?

Another example:

screen shot 2015-08-21 at 4 14 27 pm

@sethladd
Copy link
Contributor

Will see if users notice this. Can try something else if it doesn't work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P1 A high priority bug; for example, a single project is unusable or has many test failures type-enhancement A request for a change that isn't a bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants