Should cropTo be able to directly take an element as input?

[youennf]

It seems potentially useful to pass an element directly to cropTo instead of a a CropTarget, especially if CropTarget is created asynchronously.
One potential issue is if at some point, it is found good to have a CropTarget getter on the track itself.

[eladalon1983]

It seems potentially useful to pass an element directly to cropTo instead of a a CropTarget, especially if CropTarget is created asynchronously.

I think it's a good idea. It's a non-blocking ergonomics improvement that affects only some cases. I'm marking it as such.

One potential issue is if at some point, it is found good to have a CropTarget getter on the track itself.

Resolution: Make cropTo(Element) implicitly create a CropTarget behind the scenes, and the getter will return that token, with no observable difference to the program between whether cropTo(Element) or cropTo(CropTarget) was previously called.

Noteworthy: An implicitly minted CropTarget is how Chrome would implement this anyway, and most likely other UAs as well.

[jan-ivar]

See #11 (comment) for why I think this special-casing is bad, and a symptom of having an API shape so unappealing in the first place that this issue is considering adding a second one as a workaround for it.