Pauan

I just now tried the latest versions of Rust Nightly and cargo-web, and it seems to work okay for me now: ``` > rustup show Default host: x86_64-pc-windows-msvc installed toolchains...

You need to use `self.as_ref()` What the error message means is basically "this type cannot be sent to JS". With your `ISVGGeometryElement` trait, you are trying to send `Self` to...

> So as a rule, I understand that I need to use .as_ref() in the js! macro whenever self is not a leaf of the inheritance tree. You need to...

> I did underestimate the usefulness of the fineprint of the error messages I did too, when I was learning Rust. > I have come across a case now, where...

P.S. Here is all of the types which stdweb can send to JS: https://docs.rs/stdweb/0.4.12/stdweb/trait.JsSerialize.html

You'd use [`client_x`](https://docs.rs/stdweb/*/stdweb/web/event/trait.IMouseEvent.html#method.client_x) and [`client_y`](https://docs.rs/stdweb/*/stdweb/web/event/trait.IMouseEvent.html#method.client_y). They're on the [`IMouseEvent`](https://docs.rs/stdweb/*/stdweb/web/event/trait.IMouseEvent.html) trait, so that way they work on all of the mouse-related events.

Alternatively, we could have a system where sub-classes don't contain a `Reference`, instead they contain the super-class, like this: ```rust #[derive(Clone, Debug, PartialEq, Eq, ReferenceType)] #[reference(instance_of = "Foo")] struct Foo(...

@NeverGivinUp It's both. The long-term goal of compatibility with wasm-bindgen will require a **lot** of changes (including breaking changes). It will take a long time and a lot of work....

> Is there a list of tasks? I don't think so, and it's a bit hard to make such a list, since we're not even sure what all the incompatibilities...

> however it does make me somewhat uneasy that this wouldn't support multiple interfaces/mixins That's a good point, I should have addressed that in my original post. The simple fact...