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
Conversation
using `-lg` as default to avoid breaking changes
b4.beta secondary is now "grey" this reduces breaking changes
We'll need to tweak the docs as well for thinks like the variant changes, etc... |
@tmorehouse The only BIG change I've noticed was added new |
OK, that is good :-) |
Codecov Report
@@ 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
Continue to review full report at Codecov.
|
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. |
By the way, I've got a host of functional components ready, but test coverage is about 50% there. |
@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.
Awesome 50% coverage is much better than our current state :D What's your idea of merging this branch into |
.dropdown-item:focus, | ||
.dropdown-item:hover, | ||
.dropdown-header:focus { | ||
background-color: #eaeaea; |
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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?
There was a problem hiding this comment.
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?
There was a problem hiding this comment.
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
There was a problem hiding this comment.
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;
}
There was a problem hiding this comment.
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;
}
``
Dropdowns in nav-bar may need tweaking (or tweaks to the click handler for |
<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> |
There was a problem hiding this comment.
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?
There was a problem hiding this comment.
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 ;-)
There was a problem hiding this comment.
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 😆
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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
…cher Removed check for `document` in `visible` watcher, as this should only be called on client side
…pdown-select.vue Moved to components-extra
Just created PR #813 to merge in carousel changes into v4-beta branch |
@tmorehouse Fell free rebasing both when you was done. Also as of @alexsasharegan suggestion, we could merge both to |
i'll merge in carousel. and we can test |
* [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
Added it back to docs. Awesome work! carousel seems pretty much stable now than it was :) |
@tmorehouse For validation do you think we should use this method? |
lib/components/carousel.vue
Outdated
@@ -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) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
I'll tweak your changes into the carousel branch and merge it into the regular dev branch |
Nice @tmorehouse! Keeping two |
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