Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[wip] bootstrap v4-beta #811

Closed
wants to merge 28 commits into from
Closed

[wip] bootstrap v4-beta #811

wants to merge 28 commits into from

Conversation

pi0
Copy link
Member

@pi0 pi0 commented Aug 11, 2017

Let's be the first one to upgrade!

BS4 Beta release notes: https://github.com/twbs/bootstrap/releases/tag/v4.0.0-beta
BV proposed changes: #747
Popper.js migration: #287
New Docs: https://getbootstrap.com/docs/4.0/components

@pi0 pi0 changed the title bootstrap v4-beta [wip] bootstrap v4-beta Aug 11, 2017
@bootstrap-vue bootstrap-vue deleted a comment from codecov-io Aug 11, 2017
@bootstrap-vue bootstrap-vue deleted a comment from codecov-io Aug 11, 2017
@tmorehouse tmorehouse added this to the v1.0.0 milestone Aug 11, 2017
@tmorehouse
Copy link
Member

We'll need to tweak the docs as well for thinks like the variant changes, etc...

@pi0
Copy link
Member Author

pi0 commented Aug 11, 2017

@tmorehouse The only BIG change I've noticed was added new light and dark variants. (And somehow old secondary is now ~light visually)

@tmorehouse
Copy link
Member

OK, that is good :-)

@codecov-io
Copy link

codecov-io commented Aug 11, 2017

Codecov Report

Merging #811 into dev will increase coverage by 0.84%.
The diff coverage is 34.37%.

Impacted file tree graph

@@            Coverage Diff             @@
##              dev     #811      +/-   ##
==========================================
+ Coverage   39.61%   40.45%   +0.84%     
==========================================
  Files          68       67       -1     
  Lines        2209     2175      -34     
  Branches      632      618      -14     
==========================================
+ Hits          875      880       +5     
+ Misses       1172     1137      -35     
+ Partials      162      158       -4
Impacted Files Coverage Δ
lib/components/table.vue 70.05% <ø> (ø) ⬆️
lib/components/nav-item-dropdown.vue 58.33% <ø> (ø) ⬆️
lib/components/card.vue 77.77% <ø> (ø) ⬆️
lib/components/navbar.vue 53.84% <ø> (+10.09%) ⬆️
lib/components/form-select.vue 63.15% <ø> (ø) ⬆️
lib/components/button.vue 71.05% <ø> (ø) ⬆️
lib/mixins/dropdown.js 8.86% <0%> (ø) ⬆️
lib/components/tabs.vue 9.72% <100%> (ø) ⬆️
lib/components/dropdown.vue 69.23% <100%> (ø) ⬆️
lib/components/carousel-slide.vue 66.66% <100%> (+4.16%) ⬆️
... and 5 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 3fdfbff...6b4f497. Read the comment docs.

@alexsasharegan
Copy link
Member

I have to check, but the col class modifiers have changed a lot (mostly deletions). I started a 1.x.x branch a while back (and it's gonna stale with all the changes in v0.19-20), but don't you think posting Bootstrap beta related PR's to a 1.x branch is best? Then we can leave our alpha branch alive for LTS.

@alexsasharegan
Copy link
Member

By the way, I've got a host of functional components ready, but test coverage is about 50% there.

@pi0
Copy link
Member Author

pi0 commented Aug 11, 2017

@alexsasharegan Yes, this branch is intended for 1.x release too :D (Naming may be little confusing) also I think that would be better starting LTS from 1.0.0 releases.

By the way, I've got a host of functional components ready, but test coverage is about 50% there.

Awesome 50% coverage is much better than our current state :D

What's your idea of merging this branch into 1.x and start the migration to functional components now? Keeping maintenance of multiple variants/branches/forks is probably going to be much harder soon.

.dropdown-item:focus,
.dropdown-item:hover,
.dropdown-header:focus {
background-color: #eaeaea;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This line was to make focus/hover state more "obvious" since the current bootstrap css the hover state is very very subtle (and hard to tell what is focused for keyboard users, since the default hover color is almost white)

Maybe I should open an issue on Bootstrap about this.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have opened issue twbs/bootstrap#23329 regarding the hover/focus background color

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It was glitching on mouse-down state (overriding blue background) also scoped is not a good idea. But got the point. will try to revert it back with fixes.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

image

(the former bug when mouse down)

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hopefully the hover state styling will be adjusted by the bootstrap team. It is in triage mode right now.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yep. Also darken would be done without directly giving bg color.

.dropdown-item:focus:not(.active),
.dropdown-item:hover:not(.active),
.dropdown-header:focus:not(.active)
.dropdown-header:hover:not(.active) {
    /* @See https://github.com/twbs/bootstrap/issues/23329 */
    box-shadow: inset 0px 0px 400px 110px rgba(0, 0, 0, .09);
}

.dropdown-item:active,
.dropdown-header:active {
    box-shadow: initial;
}

but it might affect other things.

Hmm we could add prefix for bv class names too. You think that would be problematic?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've pushed a commit. Would please locally check that and making more fixes if needed?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For table we created a .bv-table custom class to handle some specific styling issues, which we applied to the component root element. A good alternative to scoped styles

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

could do something similar here by adding .bv-dropdown class to root of dropdown, and then targeting like this (without the need for scoped on <style>):

.bv-dropdown .dropdown-item:focus:not(.active),
.bv-dropdown .dropdown-item:hover:not(.active),
.bv-dropdown .dropdown-header:focus:not(.active)
.bv-dropdown .dropdown-header:hover:not(.active) {
    /* @See https://github.com/twbs/bootstrap/issues/23329 */
    box-shadow: inset 0px 0px 400px 110px rgba(0, 0, 0, .09);
}

.bv-dropdown .dropdown-item:active,
.bv-dropdown .dropdown-header:active {
    box-shadow: initial;
}

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should the latter part be:

.bv-dropdown .dropdown-item.active,
.bv-dropdown .dropdown-header.active {
    box-shadow: initial;
}
``

@tmorehouse
Copy link
Member

tmorehouse commented Aug 11, 2017

Dropdowns in nav-bar may need tweaking (or tweaks to the click handler for b-collapse in navbar mode), as some of the classes that are used for inspection have changed. (might be just on mobile too)

<li v-for="item in list">
<button class="dropdown-item" :click.stop.prevent="select(item)">{{item.text}}</button>
<li v-for="item in list" :key="item.text">
<button class="dropdown-item" @click.stop.prevent="select(item)">{{item.text}}</button>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this component even used anywhere?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I could probably be moved to components-extra, and it needs a lot of tweaks to get it working ;-)

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actually, I was wondering too as it is neither documented or working 😆

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Heheh... It would be a nice extra component for making html stylized select fields, but it does need a lot of work.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I just moved this to components-extra, since it is not part of base Bootstrap V4 components

Pooya Parsa and others added 4 commits August 11, 2017 21:50
@tmorehouse
Copy link
Member

Just created PR #813 to merge in carousel changes into v4-beta branch

@pi0
Copy link
Member Author

pi0 commented Aug 11, 2017

@tmorehouse Fell free rebasing both when you was done. Also as of @alexsasharegan suggestion, we could merge both to 1.x branch :) (If there is no unwanted changes in the PRs i can do that now)

@tmorehouse
Copy link
Member

i'll merge in carousel. and we can test

Pooya Parsa and others added 4 commits August 11, 2017 22:47
* [carousel-slide] content classes update

* [carousel]: Incorporate observedom mixin

Add `observedom` mixin to detect changes in slide content

* [carousel] ESLint

* [carousel] docs update

* [carousel] More fixes & features

* Update meta.json

* Update README.md

* Update carousel.vue

* update demo.js

* [carousel] update demo.html
@pi0
Copy link
Member Author

pi0 commented Aug 11, 2017

Added it back to docs. Awesome work! carousel seems pretty much stable now than it was :)

@pi0
Copy link
Member Author

pi0 commented Aug 11, 2017

@tmorehouse For validation do you think we should use this method?

@@ -195,7 +195,7 @@
// Start auto rotate slides
start() {
// Don't start if no intetrval, or if we are already running
if (!Bolean(this.interval) || this.isCycling) {
if (!Boolean(this.interval) || this.isCycling) {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@tmorehouse
Copy link
Member

I'll tweak your changes into the carousel branch and merge it into the regular dev branch

@pi0
Copy link
Member Author

pi0 commented Aug 11, 2017

Nice @tmorehouse! Keeping two 1.x and dev branches as a reference would be much better. (I'm also looking for a way merge 1.x and dev sooner)

@pi0 pi0 closed this Aug 11, 2017
@pi0 pi0 deleted the v4-beta branch August 11, 2017 19:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants