Closed nkalivoda closed 3 years ago
What browser and version number did you encounter this problem with? I can't replicate it in Chrome 85.0.4 on a Mac. The behavior for me is that the window automatically expands in width to accommodate wider trees.
On Mon, Sep 21, 2020 at 12:59 AM Nick Kalivoda notifications@github.com wrote:
This tree {a b c d e f} looks like {[.a f] b c d e} when the box is at the default width in my browser.
[image: Screen Shot 2020-09-21 at 9 55 44 AM] https://user-images.githubusercontent.com/12573882/93743734-ddcace00-fbf0-11ea-9ded-722e47d22b64.png
When I expand the box, it looks right.
[image: Screen Shot 2020-09-21 at 9 55 51 AM] https://user-images.githubusercontent.com/12573882/93743754-e6230900-fbf0-11ea-8ded-2db122ecf7d5.png
It would be better if trees with too many terminals were just partially outside of the frame, prompting one to expand it, instead of displaying as different trees.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/syntax-prosody-ot/main/issues/463, or unsubscribe https://github.com/notifications/unsubscribe-auth/AC7ROKWCOSV63WPOAA7ISM3SG4BVXANCNFSM4RUHA5NA .
--
-- Jennifer Bellik, PhD Post-doctoral researcher & lecturer UC Santa Cruz https://people.ucsc.edu/~jbellik/
Firefox 80.0.1
There is css that is relevant in spot.css but mostly at the top of interface1.html
It's possible that the UTree functions in interface1.js will also be relevant, but probably not!
This tree {a b c d e f} looks like {[.a f] b c d e} when the box is at the default width in my browser.
When I expand the box, it looks right.
It would be better if trees with too many terminals were just partially outside of the frame, prompting one to expand it, instead of displaying as different trees.