Embedding tweets

Test:

Use the Tweet button, and paste the tweet ID from the URL... like so:

HTML Code:

---

[TWEET]294803698138374146[/TWEET]

---

Now that is pretty cool.

(Hmm but can't get it to work for https://twitter.com/TheRock/status/294931429924691968 ? What am I doing wrong here?)

Hm. I can no longer edit that previous post. The entire textarea is a grey box, and none of the buttons ("save", "reply", etc) work either.

http://i.imgur.com/9m9VSNx.png

Embedding another tweet.

There's something wrong with the template, 8.

Using the [tweet] screws up the /textareas on the page somehow.

Test

aaa

EDIT: boo

Hmm, I can't replicate the problem. Everything works fine for me. I'll look into it.

Testing theory from Chrome. If I'm right, this should shit the bed.

Also, you may want to tweak the code that parses the "TWEET" tag. Right now it's case senstivie, so TWEET works, but tweet doesn't (more [a-z][A-Z] than just [a-z]). This is contrary to the way other formatting tags work (which are all, afaik, case insensitive).

And... d'oh I think I know what my problem was in those previous posts.

@number8 If you're logged in as administrator, you're likely using a different template to display individual posts. This will interfere with attempts to troubleshoot at the regular-user level.

I've replicated the problem on Safari 6 and Chrome 24. It's probably an issue with a missing /div somewhere, which is causing the formatting tool (the grey box) to render badly and block the textarea.

Not sure how that ties into the TWEET tag, but I'm only seeing the issue after embedding tweets. Other pages work fine.

I could not use Quick Reply, it was greyed out just like Irish pointed out.
Advanced mode worked just fine.

Offhand guess: This has something to do with with that extra <div class="twitter">. When a tweet is embedded in a post, the entire message is contained in that div. It might be that vB's own javascript choking on that, and either not able to parse twitter's javascript when editing, or is expecting the actual post body to be in a different location (probably the parent div).

Also, tested it in Firefox so it is choking on WebKit browsers. Not gonna touch IE. That's up to you. :D