Skip to content

[css-typed-om] Add Serializable attribute to css-typed-om objects#1102

Open
DevSDK wants to merge 2 commits into
w3c:mainfrom
DevSDK:add-serializable-typed-om
Open

[css-typed-om] Add Serializable attribute to css-typed-om objects#1102
DevSDK wants to merge 2 commits into
w3c:mainfrom
DevSDK:add-serializable-typed-om

Conversation

@DevSDK
Copy link
Copy Markdown
Contributor

@DevSDK DevSDK commented Jul 13, 2023

Fixes #1101

@w3cbot
Copy link
Copy Markdown

w3cbot commented Jul 13, 2023

svgeesus marked as non substantive for IPR from ash-nazg.

@DevSDK DevSDK marked this pull request as ready for review July 23, 2023 10:40
@DevSDK
Copy link
Copy Markdown
Contributor Author

DevSDK commented Sep 30, 2025

I think the base class that cannot be constructed should not be marked as Serializable e.g., CSSMathValue due to they seems not have instance itself. (please correct me if I missed something)

On the other hand, the spec for FileSystemDirectoryHandle [1] marks the parent interface as Serializable, which also makes sense.

So my question is: is there a general rule here? For example, if a subinterface is Serializable, must the parent interface also be Serializable?

[1] https://fs.spec.whatwg.org/#api-filesystemdirectoryhandle

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[css-typed-om] structuredClone for typed-om objects

2 participants