- Issue created by @dave reid
- Open on Drupal.org →Environment: PHP 8.2 & MySQL 8last update
over 1 year ago Not currently mergeable. - @dave-reid opened merge request.
- last update
over 1 year ago 30,144 pass, 6 fail - Status changed to Needs review
over 1 year ago 6:40pm 12 October 2023 - last update
over 1 year ago 29,619 pass, 8 fail - Status changed to Needs work
over 1 year ago 6:43pm 12 October 2023 - 🇺🇸United States smustgrave
MR 4816 is pointing to correct branch. 11.x is the current development branch of core.
If you need a hard link for 10.1 it's fine to post that but would leave a comment that it's just for 10.1
As a bug will need a test case showing the issue.
Also issue summary appears incomplete with missing parts. - 🇺🇸United States adrian_s_m
Uploading new file patch, since I set the boolean value to a string previously. This is needed for 10.1.x
- last update
over 1 year ago 29,651 pass, 6 fail - last update
over 1 year ago 30,390 pass, 6 fail - Status changed to Needs review
over 1 year ago 2:38pm 18 October 2023 - last update
over 1 year ago Patch Failed to Apply - 🇮🇳India arisen Goa
Fixed the failing tests. Uploading the patch. Please review.
- last update
over 1 year ago 29,655 pass, 6 fail - Status changed to Needs work
over 1 year ago 4:03pm 18 October 2023 - 🇸🇰Slovakia poker10
The attributes in the current form (
disabled="disabled"
/readonly="readonly"
) seems to be valid in HTML5, see: https://html.spec.whatwg.org/multipage/common-microsyntaxes.html#boolean... .They are boolean attributes and according to the specs:
2.3.2 Boolean attributes
A number of attributes are boolean attributes. The presence of a boolean attribute on an element represents the true value, and the absence of the attribute represents the false value.
If the attribute is present, its value must either be the empty string or a value that is an ASCII case-insensitive match for the attribute's canonical name, with no leading or trailing whitespace.
So this does not looks like a bug.
The patch #7 will change the output of such an attribute from:
<input disabled="disabled">
to:
<input disabled="">
If I read the specs correctly, both seems to be valid in HTML5 and looks pretty equivalent for me.
If we can achieve to have just:
<input disabled>
, then it can be a bit cleaner, but not sure if this can be achieved easily. Other option is to close this as Works as designed. Thanks! - Status changed to Needs review
over 1 year ago 12:04pm 19 October 2023 - last update
over 1 year ago Custom Commands Failed - last update
over 1 year ago Build Successful - Status changed to Needs work
over 1 year ago 1:26pm 19 October 2023 - 🇺🇸United States smustgrave
@Aditi Saraf thank you for the interest in this but this was tagged for tests and issue summary update. When moving to review please read the comments and tags to make sure it's actually ready for review
- 🇮🇳India AditiVB
@smustgrave thanks for your valuable suggestion . I will look into this .
- Status changed to Needs review
over 1 year ago 6:35am 20 October 2023 - 🇮🇳India AditiVB
Hi @smustgrave i have updated issue summary . and applied patch and interdiff #10 .
- Status changed to Needs work
over 1 year ago 9:55am 20 October 2023 - 🇸🇰Slovakia poker10
Thanks.
The patches #9 and #10 are not working and are wrong. They are setting the disabled attribute to FALSE, which is wrong and not valid HTML5. I am hiding these patches and moving back to NW.
My concerns from #8 are still valid, so please do not upload new patches which are only changing the string attribute values to boolean.