Vuetify: [Bug Report] v-layout wrapping with just "row" prop and not "wrap" prop

Created on 24 Jul 2019  路  5Comments  路  Source: vuetifyjs/vuetify

Environment

Vuetify Version: 2.0.0
Last working version: 1.5.16
Vue Version: 2.0.0
Browsers: Chrome 75.0.3770.142
OS: Windows 10

Steps to reproduce

  1. v-layout with "row" prop only
  2. place three children inside where combine flex-basis exceeds 100%

Expected Behavior

Children should be maintained on single row

Actual Behavior

Children will wrap

Reproduction Link

https://codepen.io/pklitscher/pen/rXeJmy

Other comments

.row {
    display: -webkit-box;
    display: -ms-flexbox;
    display: flex;
    -ms-flex-wrap: wrap;
    flex-wrap: wrap;
    -webkit-box-flex: 1;
    -ms-flex: 1 1 auto;
    flex: 1 1 auto;
    margin-right: -12px;
    margin-left: -12px;
}

.row css appears to have wrap set. This was not the case in 1.5.16

I had a look through the migration docs and could not see info about the change.

Sorry if this is intended behaviour and I am abusing v-layout.

Thank you for 2.0 - it's like Christmas.

documentation

Most helpful comment

@KaelWD

You're abusing v-layout, .row is part of the new grid system and was never actually needed before.

I'd like to note that the 1.x documentation explicitly used the row prop in examples... If it wasn't meant to be used/not necessary, the documentation examples probably shouldn't be consistently using it?

All 5 comments

You're abusing v-layout, .row is part of the new grid system and was never actually needed before.

eslint-plugin-vuetify will now remove it for you: https://github.com/vuetifyjs/eslint-plugin-vuetify/releases/tag/v1.0.0-beta.2

Oh sweet, cheers @KaelWD .
Good call on getting rid of row.
Row is still listed as a prop in the docs and that would be super helpful in the upgrade guide

it's pain (
image

@KaelWD

You're abusing v-layout, .row is part of the new grid system and was never actually needed before.

I'd like to note that the 1.x documentation explicitly used the row prop in examples... If it wasn't meant to be used/not necessary, the documentation examples probably shouldn't be consistently using it?

6f502dfeb27ddb8de28eb140aef8857c754b0f92

Was this page helpful?
0 / 5 - 0 ratings

Related issues

ricardovanlaarhoven picture ricardovanlaarhoven  路  3Comments

chriswa picture chriswa  路  3Comments

gluons picture gluons  路  3Comments

cawa-93 picture cawa-93  路  3Comments

paladin2005 picture paladin2005  路  3Comments