Describe the Proposal
While reviewing HTMLDocument object I realized that in both cases XML/HTML, user has no control over additional options that can be used when creating those objects from strings.
I think we should allow for that in both cases in XMLType and HTMLType (and their dsl functions) constructors, and use it later.
This way we give types users flexibility to adjust options while creating types from strings
API Adjustments
XMLType / HTMLType / xml_type / html_type - would need to accept additional int $options = 0
Are you intending to also work on proposed change?
None
Are you interested in sponsoring this change?
None
Integration & Dependencies
No response
Describe the Proposal
While reviewing HTMLDocument object I realized that in both cases XML/HTML, user has no control over additional options that can be used when creating those objects from strings.
I think we should allow for that in both cases in XMLType and HTMLType (and their dsl functions) constructors, and use it later.
This way we give types users flexibility to adjust options while creating types from strings
API Adjustments
XMLType / HTMLType / xml_type / html_type - would need to accept additional
int $options = 0Are you intending to also work on proposed change?
None
Are you interested in sponsoring this change?
None
Integration & Dependencies
No response