Problem/Motivation

In #1276908: Administrative tables are too wide for smaller screens we added a method for resizing tables for smaller screens that hides columns. This works until you get to a point where you have no more 'non-essential' columns to hide. The number of essential columns can vary .

Proposed resolution

I'm not dead set on a solution for I am a fan of the solution we came up with for Responsive Bluecheese: #2225355: Make tables responsive. It uses minimal Javascript and some clever CSS. And we don't need to worry about IE8 any more :-)

Remaining tasks

  1. Move the solution into Classy
  2. Test and debug views table listings
  3. Test and polish specific instances

User interface changes

Nicer, usable tables on small screens

API changes

No

Files: 

Comments

bdevore’s picture

This method (http://css-tricks.com/responsive-data-tables/) is more what my preference would be, but it's not bulletproof for crazy big tables. Some of this could be solved via design however...

Karmen’s picture

I think that it isn't a good idea.
Look at the way that the labels are made in this example; are very static and I think that it can be a bad practise.

Why not use media queries?

lauriii’s picture

I like @bdevores suggestion

LewisNyman’s picture

Let's put this in core: #2225355: Make tables responsive, it's an adaptation of the solution from CSS tricks

lauriii’s picture

Status: Active » Needs review
FileSize
2.8 KB
FAILED: [[SimpleTest]]: [PHP 5.4 MySQL] Setup environment: Test cancelled by admin prior to completion. View

Created the basic functionality for data attribute. This solution doesnt cover all use cases but makes it possible to start developing the frontend solution.

lauriii’s picture

FileSize
2.76 KB
FAILED: [[SimpleTest]]: [PHP 5.4 MySQL] 78,939 pass(es), 46 fail(s), and 5,865 exception(s). View

Removed kint from the patch

The last submitted patch, 5: responsive-table-2280035-5.patch, failed testing.

Status: Needs review » Needs work

The last submitted patch, 6: responsive-table-2280035-6.patch, failed testing.

lauriii’s picture

Status: Needs work » Needs review
FileSize
2.77 KB
FAILED: [[SimpleTest]]: [PHP 5.4 MySQL] 79,402 pass(es), 16 fail(s), and 5,909 exception(s). View

Rerolled. My patch affects stark even though we only need this on seven. Maybe we should move the functionality there.

Status: Needs review » Needs work

The last submitted patch, 9: responsive-table-2280035-9.patch, failed testing.

jaxxed’s picture

Status: Needs work » Needs review
FileSize
4.11 KB
PASSED: [[SimpleTest]]: [PHP 5.4 MySQL] 79,601 pass(es). View

here is a patch that pushed the -9 patch template changes to the seven theme as per instructions.

LewisNyman’s picture

I think for the time being we should keep it in Stark, because the other responsive functionality isn't Seven specific. I will work on patch #9 when I have time.

lauriii’s picture

FileSize
11.98 KB
FAILED: [[SimpleTest]]: [PHP 5.4 MySQL] 79,647 pass(es), 12 fail(s), and 0 exception(s). View

This is wrong patch. Ignore

lauriii’s picture

FileSize
5.58 KB
FAILED: [[SimpleTest]]: [PHP 5.4 MySQL] 79,961 pass(es), 5 fail(s), and 64 exception(s). View

Right patch here

The last submitted patch, 13: 1938918-menu-type-table-35.patch, failed testing.

Status: Needs review » Needs work

The last submitted patch, 14: responsive-table-2280035-13.patch, failed testing.

lauriii’s picture

Status: Needs work » Needs review
FileSize
2.49 KB
7.66 KB
PASSED: [[SimpleTest]]: [PHP 5.4 MySQL] 82,084 pass(es). View

Should work now

euphoric_mv’s picture

Status: Needs review » Reviewed & tested by the community

Tested last patch #17.
It works fine.

Only problem is that column is removed on media-screen 60em. It shouldn't be removed.

I will try to do some coding on this.

euphoric_mv’s picture

Status: Reviewed & tested by the community » Needs work
lauriii’s picture

There's also one @todo in the documentation that should be taken care of before commiting

lauriii’s picture

Issue tags: +Needs screenshots
euphoric_mv’s picture

Status: Needs work » Needs review
FileSize
8 KB
PASSED: [[SimpleTest]]: [PHP 5.4 MySQL] 80,558 pass(es). View
731 bytes
67.53 KB

I added same style on @media-screen 60em as on 37em.
Also, I added screenshot how it looks on Nexus 7 tables. By me, it looks fine.

lauriii’s picture

I think we are going to right direction! Maybe we could squeeze up the space vertically a bit?

euphoric_mv’s picture

@lauriii Yes, we can do that.
Also we can make that if there is no info icon in the row, we can hide this row.

What you think?

lauriii’s picture

The idea is that we dont hide any information. Im not sure whats the plan but I realized we shouldn't maybe fix the vertical spacing in this issue because this is only about creating solution for implementing those tables. Maybe we shouldn't dig into specific tables here and we should remove the .mobile-table from everywhere. We add the classes and fix it visually on the follow-ups.

euphoric_mv’s picture

If we want to have nice responsive tables, we need to add a javascript a little bit.
I have few examples but i don't know can i use JS.

nod_’s picture

You can always add JS, I can help with the review if you want.

euphoric_mv’s picture

We can implement something like this:
http://fooplugins.com/footable/demos/getting-started.htm

It hides columns but also has "plus" icon for showing hidden columns in cool way.
I will implement this so we can see how it looks and works.

nod_’s picture

That lib may be just over the 'fancy' line. We already have a "show all columns" thing, I'm not too happy adding another lib at this point.

Also because it's not an usual way to deal with responsive tables: a11y will need to be checked (and very likely patches will be needed upstream) then UX, then style and we're turning this smallish CSS issue into a big javascript one. Beside some JS to help the CSS I feel this is out of scope.

Feel free to open another issue to add this lib with an issue summary explaining why and all, it could be 8.1.x thing :)

LewisNyman’s picture

Status: Needs review » Needs work

The idea is that we dont hide any information. Im not sure whats the plan but I realized we shouldn't maybe fix the vertical spacing in this issue because this is only about creating solution for implementing those tables. Maybe we shouldn't dig into specific tables here and we should remove the .mobile-table from everywhere. We add the classes and fix it visually on the follow-ups.

This sounds inline with the issue summary. We don't need to add it to every table in this issue. It will be a lot easier to add the class to a few tables that don't break instead of all tables and have to fix all the tiny bugs in this issue.

Setting to needs work.

LewisNyman’s picture

Status: Needs work » Needs review
Issue tags: -Needs screenshots
FileSize
3.37 KB
9.02 KB
FAILED: [[SimpleTest]]: [PHP 5.4 MySQL] 83,818 pass(es), 8 fail(s), and 0 exception(s). View

Here's a patch with added Javascript. It runs a check on all tables to see if they are larger then the container they are in, then it adds a class. It still needs a little more styling work. It could also be a little more refined, we should run a check in the template to see if the table is responsive before we add the data-th attribute. I couldn't dump the twig variables.

subhojit777’s picture

Status: Needs review » Needs work
FileSize
17.93 KB
21.24 KB
40.97 KB
38.47 KB
30.15 KB

Before applying patch:

After applying patch:

I was also thinking we should have gray-background block regions. Currently they get mixed up with block settings.

Please consider this case. This will be good for UX.

lauriii’s picture

Thanks for testing! I think we should handle these individual situations in follow ups issues to cause overhead on rerolling the patch. How did the overall solution look like on different tables on different themes?

subhojit777’s picture

Sounds good. I just tested this with Bartik, will test with other themes today.

LewisNyman’s picture

hmm yeah the solution we have here worked really well for data driven tables but not so well for functional, drag-and-drop tables. A collapsed row that takes up a lot of height is a bit of a killer for drag and drop functionality on smaller screens, not that it was great to being with.

Do you think we could add an option for tables to trigger this functionality?

lauriii’s picture

Depends on what we want to use as trigger. Maybe we could check if there is weight set for the table. We could also add it manually for all the tables we want to use as responsive or other way around.

LewisNyman’s picture

I think it would be better to keep it explicit, so there can be a "responsive_collapse" setting for every table that people can configure

The last submitted patch, 31: reponsive-table-2280035-31.patch, failed testing.

b0unty’s picture

Issue tags: +Needs reroll
sarhugo’s picture

Issue tags: -Needs reroll
FileSize
9.15 KB
PASSED: [[SimpleTest]]: [PHP 5.4 MySQL] 88,503 pass(es). View

Rerolled patch. Solved conflicts at core/modules/views/templates/views-view-table.html.twig

sarhugo’s picture

Status: Needs work » Needs review
FileSize
8.1 KB
FAILED: [[SimpleTest]]: [PHP 5.4 MySQL] 88,087 pass(es), 6 fail(s), and 419 exception(s). View

Ignore this patch. I'm uploading a new one

sarhugo’s picture

FileSize
7.43 KB
FAILED: [[SimpleTest]]: [PHP 5.4 MySQL] 88,488 pass(es), 1 fail(s), and 419 exception(s). View

Here's an updated patch that moves the data-th attribute addition to the preprocess table function instead of adding it at the template itself. This way I think is better because you don't need to modify any test suite that includes tables to look for empty data-ths.

The last submitted patch, 44: reponsive-table-2280035-44.patch, failed testing.

Status: Needs review » Needs work

The last submitted patch, 45: reponsive-table-2280035-45.patch, failed testing.

Status: Needs work » Needs review
sarhugo’s picture

I'm getting a test failed at Drupal\field\Tests\FormTest->testFieldFormMultivalueWithRequiredRadio()
Can it be related to this issue?

Status: Needs review » Needs work

The last submitted patch, 45: reponsive-table-2280035-45.patch, failed testing.

sarhugo’s picture

Status: Needs work » Needs review
FileSize
7.4 KB
PASSED: [[SimpleTest]]: [PHP 5.4 MySQL] 88,508 pass(es). View

Found the problem. The header cell content can be a renderable array so we must assign as the cell label once it's rendered.

LewisNyman’s picture

Status: Needs review » Needs work

This is looking good. There is some tidy up we can do in the CSS

  1. +++ b/core/themes/seven/css/components/tables.css
    @@ -153,10 +153,51 @@ table.system-status-report td:nth-child(-n+2) {
    +  table.mobile-table {
    +    width: 100%;
    +    border-collapse: collapse;
    +    table-layout: fixed;
    +  }
    +
    +  table.mobile-table th {
    +    display: none;
    +  }
    +
    +  table.mobile-table td {
    +    display: block;
    +    border: none !important;
    +  }
    

    I think we can remove the 'table' element from the selectors here, also we can remove the blank line between these groups

  2. +++ b/core/themes/seven/css/components/tables.css
    @@ -153,10 +153,51 @@ table.system-status-report td:nth-child(-n+2) {
    +  .responsive-enabled.is-collapsed td {
    +    display: block;
    +    border: none !important;
    

    I don't think we need an !important here

sarhugo’s picture

Status: Needs work » Needs review
FileSize
7.35 KB
PASSED: [[SimpleTest]]: [PHP 5.4 MySQL] 88,599 pass(es). View

Applied the changes mentioned at #52
I'm not sure if we need the border declaration for 'td' but leaving in case that I'm missing something.

b0unty’s picture

/admin/people/permissions#module-node the checkboxes are aligned bit weirdly to the center
Only local images are allowed.
/admin/config/content/formats the content row beneath is aswell aligned bit oddly.
Only local images are allowed.
/admin/reports/status has an enormous sidescroll ( Not shure if this page is even related to this issue )

Overall the changes look good and those mentinoned above could be put in a seperate issue / issues

lauriii’s picture

looks like that needs some special styling..

b0unty’s picture

Status: Needs review » Needs work

dropping to needs work for those mentinoed in #54

b0unty’s picture

Issue tags: +Novice, +drupaldevdays

tagging

LewisNyman’s picture

Issue summary: View changes
Status: Needs work » Needs review
FileSize
72.57 KB
1.24 KB
8.24 KB
FAILED: [[SimpleTest]]: [PHP 5.4 MySQL] 91,028 pass(es), 431 fail(s), and 16 exception(s). View

Ok how about this. I had to override a few things to get this looking ok on draggable tables. I think we need to do some testing on different themes because I think we have too much styling in Seven for this to be functional on all themes.

Status: Needs review » Needs work

The last submitted patch, 58: responsive-table-2280035-58.patch, failed testing.

Status: Needs work » Needs review

Status: Needs review » Needs work

The last submitted patch, 58: responsive-table-2280035-58.patch, failed testing.

b0unty’s picture

Status: Needs work » Needs review
FileSize
8.24 KB
FAILED: [[SimpleTest]]: [PHP 5.4 MySQL] 91,790 pass(es), 4 fail(s), and 0 exception(s). View
575 bytes

Rerolled patch as String:: class has been removed in order to support php7

Sakthivel M’s picture

Status: Needs review » Reviewed & tested by the community
Issue tags: +ChennaiSprintWeekend
FileSize
30.15 KB
137.03 KB

before patch
img

After patch

img2

Status: Reviewed & tested by the community » Needs work

The last submitted patch, 62: responsive-table-2280035-62.patch, failed testing.

DickJohnson’s picture

Assigned: Unassigned » DickJohnson

Starting to work on reroll.

pjbaert’s picture

Assigned: DickJohnson » Unassigned
Status: Needs work » Needs review
FileSize
8.24 KB
FAILED: [[SimpleTest]]: [PHP 5.4 MySQL] 91,975 pass(es), 4 fail(s), and 0 exception(s). View

Did a quick reroll

Status: Needs review » Needs work

The last submitted patch, 66: responsive-table-2280035-66.patch, failed testing.

Status: Needs work » Needs review

Status: Needs review » Needs work

The last submitted patch, 66: responsive-table-2280035-66.patch, failed testing.

pjbaert’s picture

The patch seems to fail on the FilterAdminTest

/**
   * Tests whether filter tips page is not HTML escaped.
   */
  function testFilterTipHtmlEscape() {
    $this->drupalLogin($this->adminUser);
    global $base_url;

    // It is not possible to test the whole filter tip page.
    // Therefore we test only some parts.
    $link = '' . SafeMarkup::checkPlain(\Drupal::config('system.site')->get('name')) . '';
    $ampersand = '&';
    $link_as_code = '' . $link . '';
    $ampersand_as_code = '' . $ampersand . '';

    $this->drupalGet('filter/tips');

    $this->assertRaw('' . $link_as_code . '');
    $this->assertRaw('' . $link . '');
    $this->assertRaw('' . $ampersand_as_code . '');
    $this->assertRaw('' . $ampersand . '');
  }

I can't understand why this test failed.
Thoughts?

tim.plunkett’s picture

Status: Needs work » Needs review
FileSize
9.27 KB
PASSED: [[SimpleTest]]: [PHP 5.4 MySQL] 91,977 pass(es). View
986 bytes

You're affecting all tables in core, not just some. So you'll need to update this accordingly.

tim.plunkett’s picture

+++ b/core/modules/views/views.theme.inc
@@ -558,6 +558,11 @@ function template_preprocess_views_view_table(&$variables) {
+        $data_th = SafeMarkup::checkPlain(!empty($fields[$field]) ? $fields[$field]->label() : '');
+        $column_reference['label'] = $data_th;

This should be rewritten: $column_reference['label'] = !empty($fields[$field]) ? SafeMarkup::checkPlain($fields[$field]->label()) : '';

It's not clear how this code functions in addition to or instead of the existing responsive tables solution.
There are no code comments in the PHP or JS to explain it.

pjbaert’s picture

Status: Needs review » Needs work
emma.maria’s picture

Issue tags: +Needs screenshots

Once the code issues have been addressed, can I please have some screenshots of the Bartik theme.

Bojhan’s picture

FileSize
51.52 KB

This doesn't work in Bartik.

b0unty’s picture

diff --git a/core/themes/seven/css/components/tables.css b/core/themes/seven/css/components/tables.css

diff --git a/core/themes/seven/css/components/tables.css b/core/themes/seven/css/components/tables.css
index afc9301..47f5db9 100644

index afc9301..47f5db9 100644
--- a/core/themes/seven/css/components/tables.css

--- a/core/themes/seven/css/components/tables.css
+++ b/core/themes/seven/css/components/tables.css

+++ b/core/themes/seven/css/components/tables.css
+++ b/core/themes/seven/css/components/tables.css
@@ -134,10 +134,59 @@ th.select-all {

This files changes need to be added to bartik aswell. then bartik should work again with the patch

lauriii’s picture

Status: Needs work » Needs review
Issue tags: -Needs screenshots

Are we sure we want to tackle that here? The issue topic is "Add another responsive tables solution" so we should create a solution. Implementing this could be done later. Getting this patch in a RC phase is not possible and it would be nice to get this in before 8.1 so we shouldn't add more work for this issue.

I'm removing the Needs screenshot tag for now and setting this back to NR.

emma.maria’s picture

I would expect that responsive tables should work in Bartik also. It takes only a few clicks to find that tables are not responsive and it looks straight forward enough to use the same code as Seven. If Seven has the solution implemented the other default theme needs it also. Bartik is also a works out of the box theme. These are my thoughts on this.

emma.maria’s picture

Status: Needs review » Needs work
pjbaert’s picture

Status: Needs work » Needs review
FileSize
1.53 KB
10.74 KB
PASSED: [[SimpleTest]]: [PHP 5.4 MySQL] 94,600 pass(es). View

I added the css we add to seven's tables.css to the bartik table.css file.

b0unty’s picture

Status: Needs review » Needs work

bartik works now but the code issues mentioned in #72 have not been addressed.

b0unty’s picture

to #77 and #78, i have to agree with lauri altough its a fact that bartik is a base theme shipping with but as we can see this issue has moved very slowly so its better to have 1 working than 0 working IMO.

If the patch causes many problems with bartiks table's we should revert it and create it in another issue.

lauriii’s picture

The reason why I suggest to take Bartik out is that then we have the markup to make it work and its possible to fix later on. If we don't get the markup change in, it won't be possible to do later on.

emma.maria’s picture

If Bartik is working in #80 as said in #81 and all that is left to do is address #72 then we can add the functionality to both default themes. If it's going to be too difficult, of course raise a follow up. I'm happy to manually test this a ton for Bartik.

b0unty’s picture

Status: Needs work » Needs review
FileSize
10.86 KB
PASSED: [[SimpleTest]]: [PHP 5.4 MySQL] 95,685 pass(es). View
528 bytes

added JS comment to explain what it does as per #72

lauriii’s picture

So there is the old responsive tables solution which hides content. We need to document what happens if these both have been used on a single table.

b0unty’s picture

Here's a few screenies what happens if both are enabled on same table,

Basicly only thing it does when both are enabled is that the header row has a background.

Without this patch:

With this patch but hide not enabled:

With hide & collapse:

lauriii’s picture

Status: Needs review » Needs work

So I don't think its a good idea to have the show and hide functionality with this new responsive table because it would be very confusing for people. Maybe we can hide the show and hide functionality by default?

b0unty’s picture

Status: Needs work » Needs review
FileSize
10.86 KB
PASSED: [[SimpleTest]]: [PHP 5.4 MySQL] 95,676 pass(es). View
478 bytes

turned it off by default, lets see if test bot blows up

b0unty’s picture

Right so latest Patch disables the event binding for old responsive table solution that hides content but the code is not removed as we cannot do at this stage of d8.

LewisNyman’s picture

From what I understand it should be fine if you want to use both solutions for one table, in some situations there may be one column that you can get away with hiding but that isn't enough hidden columns to fit the table onto really narrow screens. At the width the new solution would kick in.

Does that makes sense? We should be able to have both.

lauriii’s picture

I think we are able to have both but the functionality is just really weird especially on the mobile if someone hides content.

b0unty’s picture

Maybe it could work that the new solutions kicks in when the tables overflow and there is no more "low priority" columns to hide.

b0unty’s picture

Issue tags: +Needs reroll
b0unty’s picture

Status: Needs review » Needs work
rpayanm’s picture

Status: Needs work » Needs review
FileSize
10.44 KB
FAILED: [[SimpleTest]]: [PHP 5.4 MySQL] 97,301 pass(es), 8 fail(s), and 0 exception(s). View

Please review.

Status: Needs review » Needs work

The last submitted patch, 96: 2280035-96.patch, failed testing.

Manjit.Singh’s picture

Status: Needs work » Needs review
FileSize
10.72 KB
FAILED: [[SimpleTest]]: [PHP 5.4 MySQL] 98,038 pass(es), 3 fail(s), and 427 exception(s). View

rerolling a patch, Let see what testbot thinks.

Status: Needs review » Needs work

The last submitted patch, 98: responsive-table-2280035-98.patch, failed testing.

neetu morwani’s picture

Assigned: Unassigned » neetu morwani
neetu morwani’s picture

Patch applies cleanly. Queueing the patch for retesting.

Status: Needs work » Needs review
neetu morwani’s picture

Assigned: neetu morwani » Unassigned

Status: Needs review » Needs work

The last submitted patch, 98: responsive-table-2280035-98.patch, failed testing.

sumitmadan’s picture

Status: Needs work » Needs review
FileSize
11.39 KB
FAILED: [[SimpleTest]]: [PHP 5.4 MySQL] 98,052 pass(es), 1 fail(s), and 432 exception(s). View
942 bytes

Re-rolled #98.

Status: Needs review » Needs work

The last submitted patch, 105: add_another_responsive-2280035-105.patch, failed testing.

sumitmadan’s picture

Status: Needs work » Needs review
FileSize
11.64 KB
PASSED: [[SimpleTest]]: [PHP 5.5 MySQL] 98,267 pass(es). View
1.23 KB
sumitmadan’s picture

FileSize
11.56 KB
PASSED: [[SimpleTest]]: [PHP 5.5 MySQL] 98,275 pass(es). View

Oops!! Forgot to remove drupal_set_message.

jgeryk’s picture

Issue tags: -Needs reroll

patch applies cleanly, removd needs reroll tag

LewisNyman’s picture

Status: Needs review » Needs work
FileSize
148.69 KB
158.82 KB

I tested the patch on the admin/content and people pages and it looks broken. Is it supposed to be activated on these pages? Maybe the problem is with views.


LewisNyman’s picture

Bart, Lauriii and I discussed this issue at Drupalcamp North. We agreed that module developers don't need to worry about whether this solution is enabled or not. This is different to the other solution which requires module developers to specify priority.

We do need a way for themers to globally turn off this solution. In Drupal 8, choosing Stark as your base theme means "I want to do everything myself" and choosing Classy means you want the help that Drupal offers.

We think that this functionality should be moved to Classy, so it's easy for themers to avoid this if they want to implement it themselves.

Manjit.Singh’s picture

FileSize
179.02 KB

Also can we simplify the table layout of blocks a bit more. There are lot of buttons and dropdown. I think user will get confuse while configuring blocks.

b0unty’s picture

#112. Not in this issue as it doesnt fit the scope and we want have this before RC so lets not change it.

LewisNyman’s picture

Considering how complex this issue is, it would be nice to reduce scope if we can.

opdavies’s picture

#112. Not in this issue as it doesnt fit the scope and we want have this before RC so lets not change it.

Agreed.

opdavies’s picture

We do need a way for themers to globally turn off this solution. In Drupal 8, choosing Stark as your base theme means "I want to do everything myself" and choosing Classy means you want the help that Drupal offers.

We think that this functionality should be moved to Classy, so it's easy for themers to avoid this if they want to implement it themselves.

This makes sense to me. It still gives themers the opportunity to make the choice whether to include it or not.

lauriii’s picture

There is also library alter and maybe library-remove/override thing at somepoint if someone wants to disable this even if they are extending classy :)

LewisNyman’s picture

Issue summary: View changes
LewisNyman’s picture

I updated the issue summary with the next steps:

  1. Move the solution into Classy
  2. Test and debug views table listings
  3. Test and polish specific instances
Xano’s picture

Great! Getting this out of the box makes me as a back-end developer very happy!

b0unty’s picture

Issue tags: -Novice

removed novice tag as the "to do list" is not very simple and/or clear

MattA’s picture

The last submitted patch, 108: add_another_responsive-2280035-108.patch, failed testing.

The last submitted patch, 108: add_another_responsive-2280035-108.patch, failed testing.

Manjit.Singh’s picture

Queuing #108 for 8.1 branch.

andypost’s picture

Issue tags: +Needs reroll
emma.maria’s picture

Version: 8.0.x-dev » 8.2.x-dev
andriyun’s picture

FileSize
10.98 KB

Rerolled #108
Just rereroll without checks :(

kostyashupenko’s picture

Status: Needs work » Needs review
Issue tags: -Needs reroll

Status: Needs review » Needs work

The last submitted patch, 128: add_another_responsive-2280035-128.patch, failed testing.

emma.maria’s picture

The work needed for this issue was set in #119.

1. Move the solution into Classy.

However we can't achieve the step above as Classy is frozen. Therefore this issue's direction is a bit stuck right now.

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

Drupal 8.2.0-beta1 was released on August 3, 2016, which means new developments and disruptive changes should now 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.3.x-dev » 8.4.x-dev

Drupal 8.3.0-alpha1 will be released the week of January 30, 2017, which means new developments and disruptive changes should now 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.