Tait Hoyem
Tait Hoyem
> I believe that adding such a type with the logic I mentioned above directly to atspi is beneficial because other assistive technologies may want to treat embedded links and...
Not sure I understand the first part. I don't think there is a `Signal` type? The second part is true though.
New idea, we add `UFET::from_parts_unchecked`, this will be done with a trait, obviously. This will construct the event _without_ checking the interface/method combo. This allows us to write: ```rust impl...
You are right. The examples import `atspi`, not any sub-libraries. Good catch!
Oh that's why all that funny spacing came out of nowhere, haha!
@luukvanderduim if we want this done, please add it to CI as a job so that it doesn't slowly get out of sync.
> I thought the at-spi2 registry itself tracks who registers for which events. Is that not true? As far as I can tell, yes. I think you're right. `at-spi2-core/registryd/registry.c:972 and...
All the `Value`, `Image`, `Hyperlink` and `Accessible` properties are non-const! We know this since they are things that can be changed via interaction/JS in the browser.
If you are looking at other ways to do the "if null continue, else convert to proxy" thing., you could also try `Option::from(ObjectRef).map(...).await?` or something like that :shrug:
Shout out to our extensive tests that caught a ton of the mistakes I was making along the way! I would have forgot to add the signature check if we...