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
No scroll bar for editing lengthy diary entries #330
Comments
The real problem here is that the auto growing of the text area has stopped working, most likely as a result of @samanpwbb's recent redesign work. |
The problem is https://github.com/openstreetmap/openstreetmap-website/blob/master/app/assets/stylesheets/common.css.scss#L1537 which sets the height of text areas to 100% with the That line came in with c3b8897. |
This issue also affects the textbox for sending messages. And likely other textboxes as well such as commenting on a diary entry. Furthermore, if you try to scroll using the mouse/trackpad over the textbox (if there's overflowing text), the web page scrolls instead of the textbox. FWIW, the textboxes here in Github work wonderfully and is worth emulating. |
Yes, it will affect all text boxes, and emulating github is basically what the autogrow code does if it wasn't being usurped by the |
I suggest we eliminate the auto-grow plugin. It's unpredictable and it's On Sun, Jul 14, 2013 at 11:53 AM, Tom Hughes notifications@github.comwrote:
|
...and who are you exactly? Please don't reply by email to github notifications on the rails-dev list as it impossible to tell who you are if you do that. |
@tomhughes oh, I thought I was responding to the github notification directed at me (which would have posted under my account. That was me. |
No problem. I'm happy to drop it if people think that's the best idea. |
Remove autogrow in fe2f03d. |
There's no scroll bar on the text bar/body when editing diary entries.
You can expand the text box horizontally by dragging the bottom right hand corner, but then the markdown syntax box remains in position and you still can't scroll vertically.
Tested on FF 22 and chrome 28.0.1500.68, both on ubuntu 12.04
The text was updated successfully, but these errors were encountered: