News:

Want to get involved in developing SMF? Why not lend a hand on our GitHub!

Main Menu

Safari Bug: Messages Cleared before sending

Started by smokell, November 11, 2004, 05:22:26 PM

Previous topic - Next topic

smokell

The new version of Safari (1.3 for 10.3.x and 2.0 for 10.4.x) encounters a huge bug in these forums which prevents any posting whatsoever.  As soon as you press the "post" button, the message you write is completely cleared.  You are then taken to a page that says the following:

QuoteThe following error or errors ocurred while posting this message:
The message body was left empty.

So it becomes completely impossible to post in SM forums with the new Safari.  Now right now it's only available to developers (DP5 for 1.3 and Tiger is in the dev program as well), so there shouldn't be too much talk about it.  But once they're released (1.3 should be VERY soon) I'm sure there are going to be some confused Safari users out there. 

Please let me know if there's any way I can help resolve this issue.

[Unknown]

This is a bug in Safari, then.  I don't understand why they would do such a thing.

If a textarea is NOT disabled, but is readonly, it may be used with JavaScript.  In this case, just as you post, the textarea you post in is made readonly, and then submission continues.  This is actually done in more places than just this forum software.

It is common practice to use JavaScript to not only readonly a field during submission, but also to set a readonly field before submission.  Is there any way to contact the Safari developers to ask them if they are sure they want to make such a change that will break compatibility with not only older SMF versions (as I can resolve this by treating Safari with kiddie gloves) but also many other scripts?

It makes sense not to send disabled fields.  That's logical.  But it doesn't follow for readonly ones.

-[Unknown]

smokell

I sent in a bug report to apple.  I assumed since this only happened in SMF forums that it'd be a bug with the forums.  But I did send along this thread and a description of the problem, so hopefully they can fix it before the final release.

Thanks for such a fast response.

Advertisement: