- First commit to issue fork.
- 🇺🇸United States dww
I just ran into this for a client. I opened an MR, committed #3 as the first commit, and pushed another commit to address most of @alexpott's concerns in #7. Doesn't expand test coverage, so tagging for that.
- last update
about 1 year ago 30,420 pass - 🇺🇸United States dww
Saving credit for authors (myself and @zrpnr) and reviewers (@schillerm and @alexpott).
- 🇪🇸Spain guiu.rocafort.ferrer Barcelona
guiu.rocafort.ferrer → made their first commit to this issue’s fork.
- Status changed to Needs review
11 months ago 1:01pm 27 January 2024 - 🇪🇸Spain guiu.rocafort.ferrer Barcelona
I added an additional functional test, checking that the width and height attributes are missing when the formatter settings have a null value in the width and height attributes.
I am removing the Needs tests tag, and changing the status to needs review.
- Status changed to Needs work
11 months ago 7:22pm 28 January 2024 - 🇪🇸Spain guiu.rocafort.ferrer Barcelona
The pipeline error seems to be related to this other issue ( https://www.drupal.org/project/drupal/issues/3401988 🐛 Spell-checking job fails with "Argument list too long" when too many files are changed Active ) and not with the merge request itself. The branch itself is mergeable, though.
Should we still merge the code back to the project ? Or should we make the pipeline run correctly first ?
IMO, this is a really small change, and it also have associated tests, so it should be safe to just accept the merge request.
The second option might require to merge the changes back to the issue branch, so the pipeline is updated with the fix from the issue, and then, push so it runs without hitting the error ? I am not completely sure about this.
- 🇮🇳India Akhil Babu Chengannur
Akhil Babu → made their first commit to this issue’s fork.
- 🇮🇳India Akhil Babu Chengannur
I have added one more test to validate the HTML outputted by the file formatter when only width or height is set.
- 🇮🇳India Akhil Babu Chengannur
Akhil Babu → changed the visibility of the branch 11.x to hidden.
- Status changed to Needs review
11 months ago 11:28am 30 January 2024 - Status changed to Needs work
11 months ago 11:37am 30 January 2024 - Status changed to Needs review
11 months ago 11:59am 30 January 2024 - Status changed to Needs work
11 months ago 2:50pm 31 January 2024 - 🇺🇸United States smustgrave
Seems close.
Since this is changing the current field formatter believe we will need a CR with screenshots. Screenshots could be added to the issue summary here too.
- 🇮🇳India Kanchan Bhogade
Hi,
I Have tested the latest MR !5057 on Drupal version 11.0
MR Applied successfully...Testing steps"
- Install the Drupal version 11.x
- Install the Media and Media Library core Modules
- Go to media types ->video -> manage display ->video types field format -> check for dimension field, it's mandatory
- Can check on content also, add video media for any content type, and create content by adding different size videos (video size will be fixed as in format)
- Apply MR, and check for the same
Testing Result:
For the Media type -> video ->dimention field not mandatory
It can save black and videos displayed with actual size. Also able to set fixed dimensions as per requirementAttaching screenshots and videos as #26
- Status changed to Needs review
11 months ago 6:39am 1 February 2024 - 🇮🇳India Akhil Babu Chengannur
Thanks for testing @Kanchan Bhogade.
I have updated the issue summary and created a Draft change record: https://www.drupal.org/node/3418545 →
Screenshots are added in #27 so removing the tag also I reviewed the CR it seems fine. Leaving it to someone else to review.
- Status changed to RTBC
11 months ago 3:51pm 2 February 2024 - 🇺🇸United States smustgrave
CR seems good.
Cleaned up the issue summary as the remaining tasks aren't API changes.
Also screenshots belong in the User interface changes section.
Torn if this is a feature request but will leave as is.
- Status changed to Needs work
10 months ago 9:39pm 18 February 2024 - 🇪🇸Spain guiu.rocafort.ferrer Barcelona
Hi @larowlan, thank you for your suggestions.
I changed the formatter summary text, so there is one line for each width / height attribute that has been set.
I also joined the tests for the different cases, only width, only height, both, and none, in the same test method, changing the field config and loading the page again in the same method.
Waiting to see if all the pipelines run smoothly.
- 🇪🇸Spain guiu.rocafort.ferrer Barcelona
I realized the functional test for testing the multiple width, height, both, none cases was wrong.
Fixed that in last commit. - Status changed to Needs review
10 months ago 11:13am 22 February 2024 - Status changed to RTBC
10 months ago 3:02pm 22 February 2024 - 🇪🇸Spain guiu.rocafort.ferrer Barcelona
@smustgrave sorry about that, i will do that in future ocasions. Thanks for pointing that out, i didn't know.
-
larowlan →
committed 255cd0c7 on 10.3.x
Issue #3245446 by Akhil Babu, guiu.rocafort.ferrer, dww, zrpnr, Kanchan...
-
larowlan →
committed 255cd0c7 on 10.3.x
-
larowlan →
committed bd4cf51b on 11.x
Issue #3245446 by Akhil Babu, guiu.rocafort.ferrer, dww, zrpnr, Kanchan...
-
larowlan →
committed bd4cf51b on 11.x
- 🇦🇺Australia larowlan 🇦🇺🏝.au GMT+10
Committed to 11.x and backported to 10.3.x
Published CR - Status changed to Fixed
10 months ago 1:39am 4 March 2024 - 🇧🇪Belgium wim leers Ghent 🇧🇪🇪🇺
Let's also update the config schema to match this change: 📌 Follow-up for #3245446: update `type: field.formatter.settings.file_video` to match Active .
Automatically closed - issue fixed for 2 weeks with no activity.