Wow, that's a lot Geoff is home sick today so I'll respond in his absence.
16 hours ago, Mr Crash wrote
2. Why are you creating a competetive HTML5 version ?
- browsers spell checking doesn't work
The reason for this, so I understand, is that browser spell checkers look for <textarea />s on the page and apply their functionality to that. As I explained before, in my long-winded description of how TinyMCE works, we do have <textarea />s on the page initially but TinyMCE hides these and creates it's own control in an iframe. The browser's spell checker can't reach or isn't aware of these new elements apparently. It is unfortunate but until we have a better rich text editing option (and we're open to suggestions btw), this is what we're going with.
- Long comments have a bad scroll bug - might be fixed now, i don't know
This comment of mine is pretty darn long and I don't see any scrolling problems I'm using Chrome though. I do remember IE9 Beta having an issue where if you scrolled down the page it would start repeating everything? Something like that? I think they fixed that bug in RC thoughso let us know if it does come up again.
- copy and paste is buggy in many ways (i'm using the keyboard shortcuts: ctrl+c, ctrl+v)
- 1. pasting in a long comment makes the whole page scroll down
- 2. Pasted text get different formatting ( see my previous post for example )
Interesting. #1 is by design. It's an option in TinyMCE to have the box grow as you type so that you can see what you're typing without having to scroll the box down. #2 sounds like a bug though so I will log that one as well.
- Comments lose formatting (even when the toolbar is visible)
Can you send a screenshot of this?
- Breaking up a quote doesn't work (using *snip*) Make it easier to split up quotes
Good suggestion, I'll put this in as a feature request.
Hmm... the stylesheet should be the same within the text editor as when you hit submit and view it on the page. It is pulling the exact same stylesheet I believe (global.css). I'll speak with Geoff when he's back to make sure things haven't changed. Looks the same to me though, just anecdotally. If you hit Enter it creates a new paragaph, if you hit Shift+Enter it creates a line break (<br />).
- Pressing submit button takes you back to the first post in the thread
Yes, that's true. This relates to what happens when you click the little half circle on the forum thread list (take me to my last read post). Currently that is difficult for us because of the paging. It would be simple to send someone to /forum/thread#lastreadpost if we didn't have paging but since we do, we'd have to do a query on each thread to see what page the last read post exists on and that would bring down the perf on the forum thread list page. We have other ideas on how to accomplish this such as running the query only after someone actually clicks on that circle (which I think is what we're going to go with) but just haven't implemented it yet. Hey, we've been a little busy with adding Events and whatnot But once we have that functionality, we can apply the same logic to when someone submits a new post. Let's say the last post is at the end of page 2 and your new post ends up being the first post on page 3 instead, we'd need to figure that out. Anyway, it's already a bug in our system so I'll just add to it to use the same logic for creating new posts.