Chrome textarea fail
-
Wanna see a test in which Firefox destroys Chrome?
Try pasting 500K characters or more in a textarea.
Chrome becomes unusable, while Firefox flies.
Some debugging reveals the problem is in Chrome's spellchecker, which is complete garbage and hogs everything down while it validates the text past certain size.
So just disable spellcheck for the textarea, right?
Wrong. Chrome ignores the
spellcheck=false
and similar attributes we tried.<body> <textarea id="txt" autocomplete="off" autocorrect="off" autocapitalize="off" spellcheck="false"></textarea> </body>
We are still looking into this, but as things stand, looks like we'll end up telling our users to avoid editing anything larger than 1000 lines in Chrome. Or use Firefox.
Un-fucking-believeable.
-
Try pasting 500K characters
-
People prefer to paste a bunch of CSV into the importer than deal with FTP and file uploads.
-
past a bunch of CSV
file uploads.
what is wrong with a file upload button?People prefer
Some people are idiots.
Limit the text area and provide an upload button. Small uploads can be done with the text area, for larger uploads it is necessary to upload the file.
-
Some people are idiots. Limit the text area and provide an upload button. Small uploads can be done with the text area, for larger uploads it is necessary to upload the file.
Have you tried it in Firefox and Chrome without spellchecker?
You can paste anything.
-
INB4 someone pastes the data from Excel and you have to parse that!
-
You can paste anything.
Hookonpaste
, store the data elsewhere, and paste a "[Warning ID 10T: Large amount of data, hidden for your convenience]" or something instead.@Onyx said:INB4 someone pastes the data from Excel and you have to parse that!
Can't paste a ZIP file into a textarea. However, getting the data is easy enough, it's just one XML file per sheet, and the schema is extremely simple if you don't care about formatting/pivottables/etc.
-
Can't paste a ZIP file into a textarea. However, getting the data is easy enough, it's just one XML file per sheet, and the schema is extremely simple if you don't care about formatting/pivottables/etc.
It might be worth using a different workflow where the first step is to have the user drag-and-drop their spreadsheet into the application, and then provide a way to let them go from there. Yes, it means that trivial demos get a bit more complicated, but everything that's actually meaningful to the users will get easier.
Except for the idiots who can't handle drag-and-drop.
-
You can paste images into websites as a way to upload them (Discourse for example).
Does the same API work for other types of files? That would be your solution.
-
You can paste images into websites as a way to upload them (Discourse for example).
Does the same API work for other types of files? That would be your solution.
That's not as intuitive as just pasting a bunch of text, as they are used to.
-
What could be more intuitive than drag and drop? I even drag and drop text sometimes to avoid copypasting it.
-
(shrugs) I could look into that, I guess.
-
Actually, drag'n'drop is fun and easy, nowadays. Don't know
what frameworks you're allowed to useif you're allowed to use frameworks but as far as I can tell, it's extremely easy with $() alone.
-
Say, when the source is another website, not files.
Btw, I once have to use textarea for web input of "barcode scanner on paperfeed tray" that scans the barcode as the document goes through the scanner. Not even AJAX is reliable on the response time of the website and we always missed about 5 on a stack of 5000 papers. In the end we also need to temporarily store the barcode scanner entries on textarea and postback in one go as the scan finished.
-
INB4 someone pastes the data from Excel and you have to parse that!
Parsing data pasted from Excel is 1000 times easier than uploading an Excel spreadsheet and extracting data from it. You can support older versions of Excel without running Excel server-side, no issues with telling the user to put the data on a certain sheet or in a certain cell, no dealing with formulas vs. values, easy support of processing partial data sets, and best of all - no talking to clueless users who just saved a file and can't find it to upload it.
-
TextAreas have screwed up my Android's keyboard for a while now, off and on depending on the build. You'll notice the effect sometimes if I'm on Discourse on Mobile, but it affects all sites...
Filed under: Now I need to go and clean the custom word database of suddensuddenysuddenly entries
-
Oh. I thought that was just me...
-
I'll file a bug report with Mozilla to let them know they have a Chrome defeature to implement.
-
Don't want to run Excel on your server? Do you have TRWTF of languages installed?
If you answered both of these questions, then look no further than https://github.com/PHPOffice/PHPExcel
-
-
Our code base has two copies, one is going spare if you want it.
-
Already way ahead of you:
-
I love how they have unit tests, but they don't try to make them pass.
-
Used that to generate reports about six years ago.
This was in an environment where I was literally given notepad.exe to be my IDE of choice. At least they allowed me to run a portable AMP suite.It was pretty glorious, since I didn't have the means at the time, the site was iFrame dependant, no such thing as Ajax, and was quite easily broken.
Too bad I don't have a copy of that anymore (IP after all), but it may have just made an average submission for the site...