Kris West

Note: - #1528 could be dealt with at the same time as this in the revised workflow

Kris West / interop.io 🚀

I've had similar trouble using the TS enums and migrated everything else (in generated code) to string unions recently. Hence, I support this. We had one question raised about whether...

The FDC3Event schema looks correct to me: https://github.com/finos/FDC3/blob/7abbe23703b1a07fca3d4d4495db845042da053f/packages/fdc3-schema/schemas/api/api.schema.json#L522-L539 The error is only in the typescript for FDC3Event: https://github.com/finos/FDC3/blob/7abbe23703b1a07fca3d4d4495db845042da053f/packages/fdc3-standard/src/api/Events.ts#L34-L37 and is probably not affecting anyone much as its not replicated on...

I don't see anywhere that we're handling the location info coming from the DA at the moment. It probably needs to be added - although it could go into SessionSotrage...

FYI I can make changes today or tomorrow before I disappear on vacation (sans laptop)... Hence, if anyone can have a think on this one and let me know ASAP...

I'm not convinced that you don't need a drag message. From inside the iframe you don't know your current location, but you do know how it needs to change due...

The dragging came from a StackOverflow with a nice working example thats easy to test cross-browser and @julianna-ciq had a successful play with an example I believe. The examples are...

Not entirely, as I said I don't think its workable that way round for positioning, but otherwise yes. In particular, I'm fine with the iframe sending an outward message first...

I think we can defer persisting anything for simplicity. Start by focusing on showing, styling and moving the things!