syrcro wrote:

Reproduced with Win 7 Pro SP 1 (German), Chrome 14.

steefy389 wrote:

Too clearify it: If you click the edit-Button on the stable version of a page, not the current (unstable) version of the page is edited as prior to 1.18, but instead the stableversion is opened to edit (oldid). This leads to a notice that the user isn't editing the current version, but I think that many users will just ignore the notice, edit the stable version and overwrite unstable changes.

This isn't restricted to logged-out users, it affects everybody who uses the stable version of an article as standard.

Possibly caused by r80001. Previously, the edit link did not have oldid=x in it for the stable version like this.

Fixed on site, will port to /trunk later.

Fixed in r99614.

a.d.bergi wrote:

I think a edit link should link to a form where you can edit the content you're currently seeing. What if you find an error, want to fix it, and can't find it in the source any more (and going back to view tab it's still there)?
So when we link to another version to edit than the shown, we should point that out, e.g. in the edit links tooltip.

(In reply to comment #6)

I think a edit link should link to a form where you can edit the content you're
currently seeing.

That's going to cause the same problem this bug reports. This UI change won't happen.

What if you find an error, want to fix it, and can't find it
in the source any more (and going back to view tab it's still there)?

That's what the notice in the edit form is for ("pending changes affect the area you are editing").

So when we link to another version to edit than the shown, we should point that
out, e.g. in the edit links tooltip.

No one is going to notice that.

The current behavior is back to the long-established UI behavior of the software.