I've also noticed this issue, but I donīt think the problem is
browser related - I use both IE (by choice) and Netscape
(because Konqueror is not yet ready) and I remember having
created empty nodes with both browsers ...
There would be two fix possibilities :
- Create reply nodes only at submit-time
- Remove empty nodes after some timeout (like 1 hour)
The first method would be the Right Thing, while the second method
could be accomplished by simply kludging another daemon
to the database that cleans up unreferenced empty nodes
after some expiration time (which has other implications
for the reputation and/or experience of these nodes).
| [reply] |
It's not your browser, it's just certain parts of Perlmonks. This
has already been pointed out quite a few times. A consistent posting
mechanism is needed for *anything* added to perlmonks:
- Show the original post, then the "Your reply" area (this has
been worked on lately, thanks vroom!)
- Don't award XP and/or create a new node until the Submit
button is pressed.
I avoid part of the problem by always opening replies in a new
window - which also allows me to view the entire thread
by toggling back to the previous window as I write.
| [reply] |
I avoid part of the problem by always opening replies in a new window - which also allows me to view the entire thread by toggling back to the previous
window as I write.
That's fine as a personal action, but I would argue against making that the behavior of replying in general. A site should never open a new window without a good reason, that's for the user to control.
| [reply] |
I wasn't arguing for that as a default action, just sharing
a 'personal action'. It may very well open up a new window already,
as far as I know - my javascript is always disabled. :)
| [reply] |