Max Leske

These issues would be taken care of by https://github.com/SeasideSt/Grease/pull/138, which simply introduces two extensions. But see discussion in #1159. This might not be the best solution.

I that piece of code needs to be improved. I've stumbled over the same thing when implementing streaming requests. The conditional is just not flexible enough to handle all possible...

The culprit is `WAAbstractFileLibrary class>>asSelector:`. It tries to generate a selector from the string '1-1' which would not be a legal selector. Unfortunately, the method answers `nil` in that case....

No, the current logic would create selectors `myFilev1` and `myFielv2`. The problem with `1-1` is that none of the characters are legal start characters, otherwise digits are allowed as part...

I've had the same problem before. The issue is that JSScript accept statements but does not render them.

Here's a workaround I just had to come up with (from Seaside 2.8): ``` SUStream new nextPutAll: 'document.querySelector("selector").classList.remove("class");'; javascript: (aCanvas javascript alias: 'window'; call: 'setTimeout' arguments: { (aCanvas updater "...")...

Seaside has been working in Pharo without `BlockContext` and `ContextPart` for a while already. Updating Squeak shouldn't be a huge issue.

I have a working hack wich I'm currently discussing with Sven. What I have in mind should: 1. allow a proxy server to handle the file upload 2. enable Seaside...

Thanks @nphoe! @fzipi, @theMiddleBlue I'm not convinced that adding those keywords is a good idea. Alternatively, we could - drop `is not` entirely - add a stricter rule at PL...

See #2591 for a discussion on possible integrating a script to emulate negative-lookahead.