@jidanni -- Thank You for the report.
Tested the issue on Samsung SM-J710F (Android 7.0) using Chrome Canary# 64.0.3271.3 and could not reproduce the issue.
Could you please upgrade your Chrome to Latest Canary and let us know the updated behavior and also provide us the device and OS details which would help us triaging the issue further.
Thanks in Advance.

Closing issue due to lack of feedback requested but not provided. If the issue still exists please open a new issue with the details requested.

I must have missed the notification. Anyway I found it is very easy to reproduce. All you need to do is in the GitHub issue text box for the body of the bug report, just hit a bunch of newlines and you'll see that the submit new bug button disappears! The only way to get it back is to press the very top of the page thus going to a new page, and then hitting the back button to return to the bug report and then you can see the submit new bug button.

(Are you sure I should file a new bug report? I was told that it's better to reopen issues than create duplicates. But whatever you would like I will be happy to do.)

In fact pressing any link on the page, and then pressing the back button will restore the submit new bug button. And once that button has been restored it won't go away anymore for that bug report thankfully.

I'm using the absolute newest version of Chrome Canary that I found on the Google Play store this morning. I cannot copy the version info because it's readonly alas. I believe I submitted a different bug about that.

@jidanni -- Thank You for the report.
It would be very helpful if you provide a screen cast of the issue which would help us to triage the issue further.
Thanks in Advance.

Thank you for providing more feedback. Adding requester "msrchandra@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Is this what I should do?:
https://www.labnol.org/software/record-android-screencast/4929/

Anyway how about my Comment 4? Does that reproduce it for you?

Thank you for providing more feedback. Adding requester "msrchandra@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Tested on Chrome #64.0.3282.29 on Pixel 2 Android 8 and not able to reproduce the issue by following the below steps:

1. Launch the Chrome browser.
2. Navigate to the URL: https://github.com/indywidualny/FaceSlim/issues/new
3. Enter large data of text in the "Title" and "Leave a comment" text fields.
4. Observed that "Submit new issue" is not hidden.

Please refer the below URL for screencast.

@jidanni -- Thanks for providing the feedback. Please refer the above steps and screencast and let us know if we have missed anything. You can update your Chrome to latest version #64.0.3282.29 and verify. If the issue is still reproduced please provide your device details and OS, this would help us in further triaging the issue.

If you don't have the setup for the URL provided in C#11, you can install any app from play store like DU Recorder and share screencast.

Please let us know you observations.

Thanks in advance.

Okay here you go. I did it with the version of Chrome Canary I got from the Play Store just today. Maybe it only affects ASUS Android 7.0.

Deleted: 20171223_182528.mp4 267 KB

	20171223_182528.mp4 267 KB View Download

Thank you for providing more feedback. Adding requester "pnangunoori@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

I hit the return key about 6 times. Then I hit the image of a keyboard with an arrow downwards to get the keyboard off on the screen so you can see that there's no more submit button hiding underneath anymore.

jidanni@ -- Tested using ASUS_T00J on Chrome Canary #65.0.3303.0 and couldn't reproduce the issue. Could you please share the Asus device details used by you to reproduce the issue.

Thanks in advance!

	65.0.3304.0 (Official Build) canary (32-bit)
Revision	504fd2e8f347bf20638cce9f80ebf065ad017a73-refs/heads/master@{#526164}
OS	Android 7.0.0; ASUS_Z012DA Build/NRD90M
Google Play services	SDK=11200000; Installed=11951448; Access=1p
JavaScript	V8 6.5.102
User Agent	Mozilla/5.0 (Linux; Android 7.0; ASUS_Z012DA Build/NRD90M) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3304.0 Mobile Safari/537.36

Is from  chrome://version/

Thank you for providing more feedback. Adding requester "pnangunoori@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Maybe there is some conflict with the stock 
 https://play.google.com/store/apps/details?id=com.asus.ime

Tested on latest Chrome stable #65.0.3325.109 and Canary #67.0.3368.0 on ASUS_Z00AD Android 5.0.0 and ASUS_T00J Android 4.4.4 and not able to reproduce the issue by following the below steps:

1. Launch the Chrome browser.
2. Navigate to the URL: https://github.com/indywidualny/FaceSlim/issues/new
3. Enter large data of text in the "Title" and "Leave a comment" text fields and by tapping "Return" button continuously.
4. Also, verified by tapping "Return" button continuously using "ZenUI Keyboard – Emoji, Theme" keyboard.
5. Observed that "Submit new issue" is never hidden.

Please refer the below URL for screencast.

@jidanni -- Could you please update your Chrome to latest versions and verify if the issue is still reproduced. If reproduced, could please share the LOGS of the issue.

Thanks in advance.

Deleted: 786315-2.mp4 3.2 MB

	786315-2.mp4 3.2 MB View Download

I am sorry but the exact same thing happens as I posted in comment 16 so there's no need to attach another video for me and here's a picture of the version which of course I cannot copy with a mouse because it's only a picture

Deleted: Screenshot_20180314-181737.jpg 132 KB

	Screenshot_20180314-181737.jpg 132 KB View Download

Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

As far as LOGS, a Google search leads to
https://www.chromium.org/for-testers/enable-logging which leads to
https://www.chromium.org/developers/how-tos/run-chromium-with-flags
which says "Setting Flags for Chrome on Android"
"Note that this method will only work if you are running on a rooted device OR using a debug build of Chromium."
but I did not root my phone and am only using Google Play Canary Chrome.

jidanni@ -- Please refer the below links, they may help

https://developer.android.com/studio/command-line/logcat.html
https://logmatic.io/blog/a-how-to-guide-to-debugging-with-android-logcat/
https://www.youtube.com/watch?v=P7BPxDKTHm8

Logs would help us in further triaging as the issue is not reproduced at our end even from Zenfone family devices.

Thanks!

pnangunoori@, could you try to reproduce with Android 7.0 or 8.0 in addition to
Android 4.4 and 5 (#c23)?
Because jidanni@ uses Android 7(#c20), and Android 8(#c24).

It seems this is started from Android 7.

Also, please try GBoard + Android 7/8 combination on any device.

If it works, the issue may be caused by ZenUI keyboard.

yosin@ -- Tested on Nexus 6P Android 7.1.2, Samsung J7 Android 7.0.0, Pixel and Pixel XL Android 8.1 and couldn't reproduce the issue with GBoard or Samsung keyboard.

I think it might be device specific as in C#22.

Let me know if any information is required.

Thanks!

OK next week I will see what Logcat has to say and report back here.

Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

So you want all logcat lines with webview or chromium in them?

OK here's the logcat output you requested.

Deleted: rr.log 58.2 KB

rr.log 58.2 KB View Download

The NextAction date has arrived: 2018-03-29

Mark WontFix since this is device specific or ZenUI keyboard issue per #29.

OK, I filed it at https://www.asus.com/zentalk/tw/thread-327626-1-1.html . Thanks.