Discussions

@CKurt: Dang, you're right. I use Chrome mostly so obviously it works there and it works in Safari also. I believe the sticking point is CSS3 keyframes support for this one. Firefox has it's own proprietary "@-moz-keyframes" rule that the developer could have added in there but they didn't, they just used "@-webkit-keyframes". Sounds like rounded-corners part deux to me but I guess that's how standards evolve without holding us back for lack of consensus.

Kind of proves my point though, that it's still usable in other browsers or rather there is valid content on the page rather than it being a broken page. It's pretty darn awesome in the ones that it does work in though

Have you all seen Madmanimation yet? It's all done using semantic HTML markup and CSS3 transitions. I saw Andy Clark do a talk about it at An Event Apart this year. It's the best example I've seen thus far of Flash-ish content not being done in Flash. The thing I love about the way they did this in particular is that it falls back gracefully for browsers that don't support CSS3 - they would see a screenshot and a paragraph of text describing what is happening in each key frame of the animation. This also makes the content accessible to users who are using screen readers - double awesome in my book.

If you read Anthony Calzadilla's writeup about it, you'll see that a tool is being built as a result of that project that will basically write the CSS3 transitions for you and the graceful fallback code. Can't wait to get my hands on that.

So funny! I had never played Angry Birds before. Is that just what the original version is like?

Which video in particular? I just tried one of the featured ones on the home page and it seemed to work.

@ryanb: Glad it's working well for you! Now I just have to follow through on my other promise to make this same functionality work for when you create a new post in a thread. 

Hmm.. I was able to get to them by searching for "the full stack" and checking the "Series Posts" radio button.

http://channel9.msdn.com/search?term=%22the+full+stack%22&type=Series

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 ?

 

Who's creating a competitve HTML5 version? We're not. We're using a third-party, javascript version until there is a better (hopefully HTML5 standardized) option.

• 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.

• reply and quote buttons doesn't work sometimes
• The comment control doesn't load (http://i54.tinypic.com/fatny8.png)

I'll log this one as a bug so that we can look into it. I believe both of these have to do with the javascript not loading properly. Our javascript files are hosted on a CDN as well as our images so those servers are not directly under our control. They are supposed to work every time but as you know, things happen on the web. Perhaps we can improve our fallback and try again to load it if one of the files fails to load.

• 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.

• Lines are to far apart from each other (http://i54.tinypic.com/2zqxa1h.png)

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.

No, it was weird.. in one post there were a bunch of <h5 /> tags that were not well formed. I don't know how those got there so I assume someone put them in on purpose (not much we can do about that). There does seem to be an issue where TinyMCE likes to surround  [quote /]'s with paragraph tags which ends up in invalid markup such as <p>[ quote]Some quote here.</p><p>A new paragraph here[/ quote]</p> But that doesn't seem to break the page.

That was fun. I fixed some of the html and it appears to be okay now. 

A fix was pushed up yesterday for the control which should get rid of the focus bugs that were happening in IE. We have removed the dropdown that was grabbing focus away from the textbox because it seemed unnecessary anyway. Please let us know if any of you are still having issues with the control and if so, do you still see that Format dropdown list in the toolbar?