Subsequent methods sending to brushers after with: should fail with an error

[vitormcruz]

While trying to use Seaside, I put the callback definition after a with: message sent. Only after some time I figure, looking through this page http://book.seaside.st/book/fundamentals/rendering-components/brush-structure, that with: message should always be the last one sent.

The problem is that Seasides behaves like there was no error simply ignoring my callback, which is really unintuitive, if it showed an error or warning it would improve understanding on how to use the API.

[marschall]

We once had a Slime test for this but they seem to be no longer working in the latest Pharo versions.