Problem / Motivation

Make the new HTML <input type="month" .../> element available as an FAPI element in core.

References

W3C: http://www.w3.org/TR/html5/forms.html#month-state-(type=month)

CommentFileSizeAuthor
#22 issue-month-element-1496682-22.patch2.92 KBsivaji_ganesh_jojodae
#20 issue-month-element-1496682-20.patch2.91 KBsivaji_ganesh_jojodae
#18 1496682_18.patch4.54 KBsushilkr
#15 1496682-month-element-15.patch3.51 KBskylennard
#14 1496682-month-element-14.patch3.56 KBJalandhar
#11 1496682-month-element-11.patch3.54 KBmgifford
#8 1496682-month-element-8.patch509.08 KBmgifford
#3 1496682-month-element-3.patch3.51 KBvijaycs85

Comments

hansyg’s picture

hansyg commented
Issue tags: +html5

tagging

mgifford’s picture

mgifford
he/him
Primary language English
commented

See - #675348-64: META: Support HTML5 form input elements

Tor Arne Thune’s picture

Tor Arne Thune commented
Issue summary: View changes

Updating broken link.

Tor Arne Thune’s picture

Tor Arne Thune commented
Issue summary: View changes

Making it a link.

vijaycs85’s picture

vijaycs85
Location London, UK
commented
Issue summary: View changes
Status: Active » Needs review
StatusFileSize
new 1496682-month-element-3.patch3.51 KB

Initial patch...

mgifford’s picture

mgifford
he/him
Primary language English
commented
Parent issue: » #675348: META: Support HTML5 form input elements

Thanks @vijaycs85 - adding related node.

Status: Needs review » Needs work

The last submitted patch, 3: 1496682-month-element-3.patch, failed testing.

mr.baileys’s picture

mr.baileys
Primary language Dutch
Location 🇧🇪 (Ghent)
commented
Status: Needs work » Needs review

3: 1496682-month-element-3.patch queued for re-testing.

Status: Needs review » Needs work

The last submitted patch, 3: 1496682-month-element-3.patch, failed testing.

mgifford’s picture

mgifford
he/him
Primary language English
commented
StatusFileSize
new 1496682-month-element-8.patch509.08 KB

just a re-roll

mgifford’s picture

mgifford
he/him
Primary language English
commented
Status: Needs work » Needs review

Status: Needs review » Needs work

The last submitted patch, 8: 1496682-month-element-8.patch, failed testing.

mgifford’s picture

mgifford
he/him
Primary language English
commented
StatusFileSize
new 1496682-month-element-11.patch3.54 KB

#8 was very wrong.

mgifford’s picture

mgifford
he/him
Primary language English
commented
Status: Needs work » Needs review
mgifford’s picture

mgifford
he/him
Primary language English
commented
Status: Needs review » Needs work
Issue tags: +Needs reroll
Jalandhar’s picture

Jalandhar commented
Status: Needs work » Needs review
StatusFileSize
new 1496682-month-element-14.patch3.56 KB

Here is the re-rolled patch

skylennard’s picture

skylennard commented
StatusFileSize
new 1496682-month-element-15.patch3.51 KB

re-rolled patch from comment #14

skylennard’s picture

skylennard commented
Issue tags: -Needs reroll
Jalandhar’s picture

Jalandhar commented
Status: Needs review » Needs work
Issue tags: +Needs reroll

Patch #15, needs reroll.

sushilkr’s picture

sushilkr commented
Status: Needs work » Needs review
StatusFileSize
new 1496682_18.patch4.54 KB

Rerolled

Status: Needs review » Needs work

The last submitted patch, 18: 1496682_18.patch, failed testing.

sivaji_ganesh_jojodae’s picture

sivaji_ganesh_jojodae commented
Status: Needs work » Needs review
Issue tags: -Needs reroll
StatusFileSize
new issue-month-element-1496682-20.patch2.91 KB

Status: Needs review » Needs work

The last submitted patch, 20: issue-month-element-1496682-20.patch, failed testing.

sivaji_ganesh_jojodae’s picture

sivaji_ganesh_jojodae commented
Status: Needs work » Needs review
StatusFileSize
new issue-month-element-1496682-22.patch2.92 KB

Status: Needs review » Needs work

The last submitted patch, 22: issue-month-element-1496682-22.patch, failed testing.

mgifford’s picture

mgifford
he/him
Primary language English
commented

Is this still part of the W3C Recommendation as of 28 October 2014? I thought it had been removed.

mgifford’s picture

mgifford
he/him
Primary language English
commented
Status: Needs work » Postponed

Let's mark this postponed until it's clear that it is supported by the W3C and maybe http://caniuse.com

Version: 8.0.x-dev » 8.1.x-dev

Drupal 8.0.6 was released on April 6 and is the final bugfix release for the Drupal 8.0.x series. Drupal 8.0.x will not receive any further development aside from security fixes. Drupal 8.1.0-rc1 is now available and sites should prepare to update to 8.1.0.

Bug reports should be targeted against the 8.1.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.1.x-dev » 8.2.x-dev

Drupal 8.1.9 was released on September 7 and is the final bugfix release for the Drupal 8.1.x series. Drupal 8.1.x will not receive any further development aside from security fixes. Drupal 8.2.0-rc1 is now available and sites should prepare to upgrade to 8.2.0.

Bug reports should be targeted against the 8.2.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.6 was released on February 1, 2017 and is the final full bugfix release for the Drupal 8.2.x series. Drupal 8.2.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.3.0 on April 5, 2017. (Drupal 8.3.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.3.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.6 was released on August 2, 2017 and is the final full bugfix release for the Drupal 8.3.x series. Drupal 8.3.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.4.0 on October 4, 2017. (Drupal 8.4.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.4.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.4 was released on January 3, 2018 and is the final full bugfix release for the Drupal 8.4.x series. Drupal 8.4.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.5.0 on March 7, 2018. (Drupal 8.5.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.5.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.6 was released on August 1, 2018 and is the final bugfix release for the Drupal 8.5.x series. Drupal 8.5.x will not receive any further development aside from security fixes. Sites should prepare to update to 8.6.0 on September 5, 2018. (Drupal 8.6.0-rc1 is available for testing.)

Bug reports should be targeted against the 8.6.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

dpi’s picture

dpi
Location Perth, Australia
commented
Version: 8.6.x-dev » 8.7.x-dev
Status: Postponed » Active

Over 80% support, Firefox being the outlier citing lack of internal resources. (CIU note: most partial support is in iOS Safari, where partial refers to week only)

Version: 8.7.x-dev » 8.8.x-dev

Drupal 8.7.0-alpha1 will be released the week of March 11, 2019, which means new developments and disruptive changes should now be targeted against the 8.8.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.0-alpha1 will be released the week of October 14th, 2019, which means new developments and disruptive changes should now be targeted against the 8.9.x-dev branch. (Any changes to 8.9.x will also be committed to 9.0.x in preparation for Drupal 9’s release, but some changes like significant feature additions will be deferred to 9.1.x.). For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.9.x-dev » 9.1.x-dev

Drupal 8.9.0-beta1 was released on March 20, 2020. 8.9.x is the final, long-term support (LTS) minor release of Drupal 8, which means new developments and disruptive changes should now be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 9.1.x-dev » 9.2.x-dev

Drupal 9.1.0-alpha1 will be released the week of October 19, 2020, which means new developments and disruptive changes should now be targeted for the 9.2.x-dev branch. For more information see the Drupal 9 minor version schedule and the Allowed changes during the Drupal 9 release cycle.

Version: 9.2.x-dev » 9.3.x-dev

Drupal 9.2.0-alpha1 will be released the week of May 3, 2021, which means new developments and disruptive changes should now be targeted for the 9.3.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.0-rc1 was released on November 26, 2021, which means new developments and disruptive changes should now be targeted for the 9.4.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.0-alpha1 was released on May 6, 2022, which means new developments and disruptive changes should now be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.5.x-dev » 10.1.x-dev

Drupal 9.5.0-beta2 and Drupal 10.0.0-beta2 were released on September 29, 2022, which means new developments and disruptive changes should now be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 10.1.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch, which currently accepts only minor-version allowed changes. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 11.x-dev » main

Drupal core is now using the main branch as the primary development branch. New developments and disruptive changes should now be targeted to the main branch.

Read more in the announcement.

smustgrave’s picture

smustgrave commented
Status: Active » Postponed (maintainer needs more info)
Issue tags: +stale-issue-cleanup

Thank you for sharing your idea for improving Drupal.

We are working to decide if this proposal meets the Criteria for evaluating proposed changes. There hasn't been any discussion here for over 8 years which suggests that this has either been implemented or there is no community support. Your thoughts on this will allow a decision to be made.

Since we need more information to move forward with this issue, the status is now Postponed (maintainer needs more info). If we don't receive additional information to help with the issue, it may be closed after three months.

Thanks!