You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 8, 2024. It is now read-only.
As XAML Standard is developed, can the standard spec file include the specific list of members that each control must support to implement the XAML Standard?
As a developer of another XAML-based UI that's planning on trying to support XAML Standard, it's really difficult to make sure we're implementing our XAML Standard controls with the correct behavior without knowing exactly which properties/events are required by the standard.
The text was updated successfully, but these errors were encountered:
That's an obvious requirement for any reasonable interoperability via standard specification which even indirectly involves an API. It is possible to define XAML standard with restricting it only to xaml declarations, nevertheless, to achive anything close to interoperability an API standard is a must.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
As XAML Standard is developed, can the standard spec file include the specific list of members that each control must support to implement the XAML Standard?
As a developer of another XAML-based UI that's planning on trying to support XAML Standard, it's really difficult to make sure we're implementing our XAML Standard controls with the correct behavior without knowing exactly which properties/events are required by the standard.
The text was updated successfully, but these errors were encountered: