-
Notifications
You must be signed in to change notification settings - Fork 7.5k
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
Pure css slider handles #2132
Pure css slider handles #2132
Conversation
fa08270
to
0f06c0f
Compare
Because you can drag it half out of the player, yeah? Can you post a screen shot of that? |
Yes, precisely. I would need to actually fix the old skin to post a screenshot, but yes, the issue is that the slider handle would be absolutely positioned on the center of the end of the progress bar. That's great for the current skin, pretty crappy for the old skin. I guess the kicker is how much we care about the old skin working directly out of the box, and how much we want the slider handle to be its own component. |
This doesn't negate what you're saying but I think we should care a lot I'm not sure exactly how this fits in, but there's also the "handle" that On Thu, May 7, 2015 at 9:44 PM, Matthew McClure notifications@github.com
|
I agree, I'm just torn on how we should address that issue in particular. Note, this makes some styles easier since we don't have the weird adjusted play progress anymore. The whole scrubbing thing isn't affected at all by this change imo, since we'd still need to account for max right / left positioning. I will say, I don't think we should let "ease of current YouTube skin implementation" affect our decision. Skins change, including the YouTube skin. The new skin preview I've got enabled doesn't have an end-to-end progress bar (you can try it out by editing a cookie), but who knows what the actual styles will end up being. |
Awkward note, those are definitely the Material UI icons (or very close), so we'll be twins there either way. |
Ha, funny. I guess they ran into the same handle issue. Kind of a bummer about the icons. The more differentiation the better in the base theme, but I can live with it. So can we:
Is there any issues clicking directly on the CSS handle and dragging it? i.e. blocking the mouse tracking for the progress bar below it? |
The problem with just leaving the handle in is that, at the moment, the handle and progress bar are dependent on each other. If we want to make the CSS version the default, I think we should break the handle out into a plugin (or something along those lines) |
Yeah, that's what I meant by "make the handle independent of the slider". I still think it should be in by default, but add it as a progress bar child like the load progress bar is being added. It's no longer a piece of slider but instead specific to the progress bar. And then like the second volume control, make it hidden by default. |
In #videojs chat we landed on trying to create the max-left/right for the handle using the CSS-created handle. If that's for some reason impossible we can fall back to the separate handle component idea. |
0f06c0f
to
4579d02
Compare
4579d02
to
deb7ad8
Compare
@heff Want to take another look at this one? Through other conversations we've decided to drop everything but css-only handles for now. If there are requests to bring back the handle classes or other needs that this makes more difficult we'll tackle them down the road. Consider that can kicked. |
.video-js .vjs-slider-vertical .vjs-volume-level { | ||
width: 0.3em; | ||
|
||
&:before { |
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 might be helpful to add some comments around these to make it clear that it's the handle being affected here. It's not obvious at first glance.
Man, that's a good chunk of code removed. Looks good to me. |
deb7ad8
to
c134e30
Compare
Just an update, after debugging a few unrelated issues with @heff, this is working in IE8 now. However, we've uncovered a few other bugs while in IE8 that I'll open separate issues for. The other changes that need to be made seem unrelated. Should we pull this in in the meantime? |
Opening to review the idea, do not merge
We've talked about this in the past, but in starting to work on #2117 I realized that this would simplify my work there. We've talked about this in the past, but I just wanted to formally open this conversation and get feedback.
Pros
Cons