Antonio Salazar Cardozo

Ohai Scala 2.11. Looks like still some cleanup to be done. Will circle back!

> this is acceptable Don’t know what I was thinking. Minor releases are API-compatible, by definition. So... that’s awkward heh. Will noodle.

Moved this to hypothetical 4.0 for now… Really bummed about it though :(

(May be worth discussing if this is worth doing an earlier-than-expected 4.0 release with the community… Perhaps after another couple of minor releases.)

Not much to update here, tbh. This PR was left open because it can't land before a 4.0 release; it may have some merge conflicts but I suspect I'd be...

We've used some hacky code to make this happen internally at Elemica (it just mocks a session), so I may try to have a look at this one. Unless @farmdawgnation...

< headscratch > This seems like exactly the behavior that that variable is meant to set up? O.o

Believe this happens in [`Html5Writer.writeAttributes`](https://github.com/lift/framework/blob/5033c8798d4444f81996199c10ea330770e47fbc/core/util/src/main/scala/net/liftweb/util/HtmlParser.scala#L43), in addition to the quoted segment of [`Html5Writer.write`](https://github.com/lift/framework/blob/5033c8798d4444f81996199c10ea330770e47fbc/core/util/src/main/scala/net/liftweb/util/HtmlParser.scala#L199-L214).

Should we instead look to change how `MappedPassword` works for Lift 3?

This could be a simple matter of updating the [`ajaxOnFailure` callback in `lift.js`](https://github.com/lift/framework/blob/master/web/webkit/src/main/resources/toserve/lift.js#L52) to be passed some additional parameters [when it is invoked](https://github.com/lift/framework/blob/master/web/webkit/src/main/resources/toserve/lift.js#L256). However, the question is *how* those parameters...