Skip to content
This repository has been archived by the owner on Jul 21, 2023. It is now read-only.

wider schedule #349

Open
JuliaLawall opened this issue Aug 19, 2021 · 2 comments
Open

wider schedule #349

JuliaLawall opened this issue Aug 19, 2021 · 2 comments
Labels
A-schedule Area: schedule and events C-bug Category: something isn't working M-needs-repro Meta: needs reproduction case S-frontend Service: frontend T-user-interface Theme: user interface

Comments

@JuliaLawall
Copy link

I have a normal 14 inch laptop screen, and it looks like the schedule for ESEC/FSE is around 5 inches wide. With the long paper titles and the many author names, this means that one can see only a few talks at a time. Furthermore, it makes the scroll bar rather small and hard to use. If the schedule would use the whole width of the screen it would be more usable.

I am using Ubuntu and Firefox.

@JuliaLawall JuliaLawall added the M-needs-triage Meta: needs triage label Aug 19, 2021
@rossng
Copy link
Member

rossng commented Aug 19, 2021

Thanks for the feedback on Clowdr's schedule view. It sounds like things aren't displaying quite as we intended.

I've just had a look at the schedule on my 13" laptop screen. If anything, it's the available height that is more constrained for me - the width does not appear to be too problematic.

Would you be able to upload a screenshot showing what you experience? Ideally in a fairly busy section of the program with several parallel tracks.

@rossng rossng added A-schedule Area: schedule and events C-bug Category: something isn't working M-needs-repro Meta: needs reproduction case S-frontend Service: frontend T-user-interface Theme: user interface and removed M-needs-triage Meta: needs triage labels Aug 19, 2021
@JuliaLawall
Copy link
Author

JuliaLawall commented Aug 20, 2021 via email

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
A-schedule Area: schedule and events C-bug Category: something isn't working M-needs-repro Meta: needs reproduction case S-frontend Service: frontend T-user-interface Theme: user interface
Development

No branches or pull requests

2 participants