New comment entry widget
I'm surprised I'm the first to mention this, but the new comment/reply entry box took me rather by surprise today.
I'm probably going to be called a Luddite for this, but can I make a request for the ability to choose between the new and old methods (preferably by a setting on the member profile) if this is at all technically feasible?
I know the new input widget is probably more user-friendly and allows richer content etc., but
a) it's noticeably slow on my quad-core work box with 4GB of RAM
b) inserting things like links (which I do a lot) and just pasting text takes longer than it used to- once you know the code it becomes second nature
c) it means I now can't comment at all from my mobile device, and I can't be the only one.
Thoughts from those with comment counts in the multi-thousands and (if any find the thread) new arrivals?
I'm probably going to be called a Luddite for this, but can I make a request for the ability to choose between the new and old methods (preferably by a setting on the member profile) if this is at all technically feasible?
I know the new input widget is probably more user-friendly and allows richer content etc., but
a) it's noticeably slow on my quad-core work box with 4GB of RAM
b) inserting things like links (which I do a lot) and just pasting text takes longer than it used to- once you know the code it becomes second nature
c) it means I now can't comment at all from my mobile device, and I can't be the only one.
Thoughts from those with comment counts in the multi-thousands and (if any find the thread) new arrivals?
12
comments
|
Add Comment
|
sort by:
active |
newest |
oldest
I can't reply to comments on my computer. (I'm not sure about on other computers)
I also have to refresh the page to post a comment sometimes.
I also have to refresh the page to post a comment sometimes.
I notice a number of people's comments appear to have had the HTML reverted from them- at first I took it for someone accidentally putting tags in the comment text while not in source mode but it looks like it's more widespread than that.
I'm not at all surprised to see that my 1995-homepage post abusing tables and other tags has been un-HTML-ified, and some of the <big><big><big><big><big><big> etc. ones.
Could we have a clarification of which HTML we are allowed to use in source mode? I'm not complaining here, just don't want to keep setting off some alert somewhere saying "someone's trying to do XSS attacks with HTML comments". I'd also hate to fail some verification thing because I don't close a <br> tag or something like that.
Cross-posted to "How do you like the new editor"
I'm not at all surprised to see that my 1995-homepage post abusing tables and other tags has been un-HTML-ified, and some of the <big><big><big><big><big><big> etc. ones.
Could we have a clarification of which HTML we are allowed to use in source mode? I'm not complaining here, just don't want to keep setting off some alert somewhere saying "someone's trying to do XSS attacks with HTML comments". I'd also hate to fail some verification thing because I don't close a <br> tag or something like that.
Cross-posted to "How do you like the new editor"
This is the "double conversion" bug http://www.instructables.com/community/Double-conversion-bug-Comments-from-12-13-Oct-20/ .
It looks like what happened was that their automatic processing job to convert the whole database to the new editor's format got carried away. It picked up comments written after CKEditor was deployed, and interpreted them as needing "literal conversion."
It looks like what happened was that their automatic processing job to convert the whole database to the new editor's format got carried away. It picked up comments written after CKEditor was deployed, and interpreted them as needing "literal conversion."
Good catch sir! I assumed it was an artifact of some sort of "OK allowing arbitrary HTML is like giving power tools to exciteable 8-year-olds, maybe we'll turn it down a touch" change to the editor.
I'd still like a clarification of what (if anything) is verboten, but if we're allowed regular formatting stuff then I'm unlikely to come across anything that is. I'm hoping there's a sensible anti-XSS filter on comments because CKEditor explicitly don't supply one, but that shouldn't affect genuine comments anyway.
I'd still like a clarification of what (if anything) is verboten, but if we're allowed regular formatting stuff then I'm unlikely to come across anything that is. I'm hoping there's a sensible anti-XSS filter on comments because CKEditor explicitly don't supply one, but that shouldn't affect genuine comments anyway.
Also see Eric's <a href="http://www.instructables.com/community/How-Do-You-Like-the-New-Editor/">solicitation for comments</a>.
What mobile device are you using?
Unfortunately, no we cannot have both editors running simultaneously. They use different formats, so we actually needed to convert all the old style formatting to the new style.
Unfortunately, no we cannot have both editors running simultaneously. They use different formats, so we actually needed to convert all the old style formatting to the new style.
Argh. That means all of the FAQ stuff about formatting is now obsolete, including the <a href="http://www.instructables.com/id/Instructables_Text_Formatting/">Formatting I'ble</a>. Pity we didn't get a heads-up about it :-( <br /><br />I hope that you all (Rachel? Ed?) will be able to provide replacement documentation, rather than waiting for community members to reverse-engineer what's going on, and what works vs. doesn't work.<br /><br />Heh...just found the first bug :-) It inserts an extraneous blank space following a link, even when there's sentence punctuation adjacent (see the second line above).<br /><br />
Ah- architectural change. Well, I'll probably just use less formatting in future. I figured it was worth asking just so it could be on the record.
The device is a Nokia N770 running Maemo- it might just be a javascript problem, but it actually never got on that well with the site in the first place. Cue gmjhowe telling me to just buy an iPhone already :)
The device is a Nokia N770 running Maemo- it might just be a javascript problem, but it actually never got on that well with the site in the first place. Cue gmjhowe telling me to just buy an iPhone already :)
Does not work on iPhone OS 3.1 either. It loads the box, quite quickly, but then it never places a cursor and brings up the keyboard.
I created a bug report about this before I saw PKM's posting. Even on a good broadband connection, bringing up the editor is really, really slow.
 |
Vancouver Mini Maker Faire 2012
Rebuilding NordicTrack ski machine drive rollers
Looking for New Zealand-based Instructables authors for conference on August 27 in Wellington
Call to makers - Brighton Mini Maker Faire
Milk Crates - not as green as you think
TEDxBaghdad - Iraq - violence, dust storms and open sourced manufacturing
UK Mini Maker Faire - The Derby Silk Mill - New Poster to Share!
