3.5.0 Almost...

[Chris M]

I'd also love to find out why people get the "Please click one of the Quick Reply icons in the posts above to activate Quick Reply." rather than their actual message.

I'll have to sit and read through the code to find any possible places it could happen.

That has happened to me several times here and on my own site - I found it rather annoying

Satan

[Onimua]

Ah, so it is a bug. Thought it was random collection of people saying the same thing about how to use the Quick Reply.

[Chris M]

Ah, so it is a bug. Thought it was random collection of people saying the same thing about how to use the Quick Reply.

I think it occurs through a javascript error, where the message in the box by default does not actually get unset - It appears to have been disabled, and the user can type, but it sends the default message instead...

Just theorising though

Satan

[MGM]

I thought doing a hard refresh would fix that?

MGM out

[Onimua]

I thought doing a hard refresh would fix that?

MGM out

It's still happening, really. I'm seeing it frequently around here. Hasn't happened to me though.

[Chris M]

Hard refreshing faulty code will not solve the problem...

I actually believe it more to be an inherant problem with Javascript than with the way it is being used...

Satan

[Scott MacVicar]

Its not faulty code, I'm pretty sure of that. I've never been able to reproduce it but I think it might be something thats system specific. I'm still thinking cache though.

If someone experiences it I'd love to see what their JavaScript Console said.

[Oblivion Knight]

It's quite obvious that there will be an RC3, there's sufficient bug reports that's both Closed (fixed) and Awaiting Feedback that warrants an RC3 release.

Agreed, I think we'll definately see an RC3 version at the very least. Possibly RC4 depending on any potential issues that may arise from the new hook placements and such..

[Floris]

I predict it will be before the end of this year.

[RagingPenguin]

I say one to two weeks of running the current version here, with bug count at zero (confirmed and unconfirmed), to make sure.

[Chris M]

Its not faulty code, I'm pretty sure of that. I've never been able to reproduce it but I think it might be something thats system specific. I'm still thinking cache though.

If someone experiences it I'd love to see what their JavaScript Console said.

Well you are right about it being system-specific - It does not happen with FireFox (for me at least) but does with IE...

It for some reason seems to be targetting me several times on my local board then dissapearing, then re-appearing - So far no errors appear

It may not be faulty code in the strictest sense of the word, just that it's not correct code to be using for IE...

Satan

[Starsurfer]

Never seen it happen

[Scott MacVicar]

You see the iframe isn't really submitted when we post so on the onsubmit handler we grab the content and shove it in a hidden field, if that stage didn't happen then obviously something went horribly wrong.

I'm looking to see how it could happen before I find out why.

[Scott MacVicar]

So the only thing that can cause this is get_editor_contents() returning the wrong textarea value since we maintain a regular textarea hidden away. I'm going to play switching editor types etc to see If i can reproduce this.

[James Kojiro]

Starsurfer, you were wrong.
That's a Karate outfit, Scott