-
Notifications
You must be signed in to change notification settings - Fork 90
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
Fix issues 132 and 151 #152
base: master
Are you sure you want to change the base?
Conversation
@@ -133,8 +133,6 @@ if(modeEnabled('translation')) { | |||
synchronizeTextareaHeights(); | |||
}); | |||
|
|||
$(window).resize(synchronizeTextareaHeights); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Did you figure out why this was added using git blame? I'm concerned about removing it without knowing why in case we regress on another front.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Um, Nop! I tried to figure out the code that was causing this. I will use git blame
now!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Using git blame, it shows that you have made the latest modification to that line with commit message as in this link. How do I infer from this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think that commit just fixed a bunch of style issues. You'll have to look backwards in time a bit.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure on it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Um, the commit message says - Improve textarea mechanics
.
The link to the blame where this line of code was added it link
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Well, that's not a helpful commit message.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm yeah. But I believe removing it should not cause an issue right? As in, it is just synchronizing heights! We could add it very easily in the event we need it. Inputs?
I might also want the textarea to not decrease if I increase it manually then type something. Some max approach? I need to think about the ideal behavior of this more... I remember when we added auto-adjusting text boxes, I was hesitant but didn't really have much time to go through it with a more critical eye... The behavior is hard to get right. |
I would wait on this to get the behaviour right :D |
How about this: The Text deletion:
Text addition:
|
By the way, I de-conflicted the PR in https://github.com/Androbin/apertium-html-tools/commit/604892df5f311e285e03951f7b3f1cbe65c8940c |
Is the space |
I define |
Hmmm, what happens if I paste a block of text then? |
I can think of three basic options:
|
We could also ensure that |
This isn't great. It shouldn't keep growing without a max-width. |
@sushain97 We are talking about height, aren't we? |
But yeah, we could just use these CSS properties:
|
Oops, yes. I meant width.
Indeed. But this needs to be taken into account in the JS as well since |
No description provided.