Re: [css-d] anyway to style tag?

[Brian Kardell]

On Mar 14, 2017 6:36 PM, "Angela French"  wrote:

Hello,
I am experimenting with using the  tag.  I see it looks very
different across browsers.  Is there any way to consistently style it
across browsers?  Everything I see from Google is years old.

Thanks,



Angela French
Internet/Intranet Specialist
Washington State Board for Community and Technical Colleges
360-704-4316
afre...@sbctc.edu
www.sbctc.edu



What exactly are you looking to style? The player controls?


__
css-discuss [css-d@lists.css-discuss.org]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
List policies -- http://css-discuss.org/policies.html
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
__
css-discuss [css-d@lists.css-discuss.org]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
List policies -- http://css-discuss.org/policies.html
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/

Re: [css-d] Select by descendant?

[Brian Kardell]

CSS selectors level 4 introduces a :has() pseudo class, but it isn't out
there and even when it is it will (initially at least) only be supported in
the complete profile - meaning it will work via querySelectorAll and
friends, but not CSS itself.

If you only, need this in script, jQuery has had :has from the beginning
(it was a proposal from CSS3 a decade and a half ago), and if you need it
in CSS you might have a look at hitchjs which has it
On May 16, 2014 5:53 AM, BPJ b...@melroch.se wrote:

 is it possible to select an element based on the presence or absence of a
 descendant with some attribute?

 /bpj
 __
 css-discuss [css-d@lists.css-discuss.org]
 http://www.css-discuss.org/mailman/listinfo/css-d
 List wiki/FAQ -- http://css-discuss.incutio.com/
 List policies -- http://css-discuss.org/policies.html
 Supported by evolt.org -- http://www.evolt.org/help_support_evolt/

__
css-discuss [css-d@lists.css-discuss.org]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
List policies -- http://css-discuss.org/policies.html
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/

Re: [css-d] Select by descendant?

[Brian Kardell]

On May 16, 2014 9:47 AM, MiB digital.disc...@gmail.com wrote:


 may 16 2014 14:25 Brian Kardell bkard...@gmail.com:

  If you only, need this in script, jQuery has had :has from the beginning
  (it was a proposal from CSS3 a decade and a half ago), and if you need
it
  in CSS you might have a look at hitchjs which has it


 I suppose that if you are already using jQuery you could make a script
add a class or whatever to the parent element.  While this is cheating
(:-P) it will work unless Javascript is inactive.


That will get you the basic onload of it, sure.  If you wanted it in css
though then you want to maintain that class appropriately (if the :has
ceases to apply at any time or starts to) and that's more work... That's
what hitch does, and let you write it in CSS...  Also to use it like you
would and find out if it's really as useful/intuitive as you imagine and,
hopefully, provide feedback to www-st...@w3.org (css working group) -
extensiblewebmanifesto.org

__
 css-discuss [css-d@lists.css-discuss.org]
 http://www.css-discuss.org/mailman/listinfo/css-d
 List wiki/FAQ -- http://css-discuss.incutio.com/
 List policies -- http://css-discuss.org/policies.html
 Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
__
css-discuss [css-d@lists.css-discuss.org]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
List policies -- http://css-discuss.org/policies.html
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/

Re: [css-d] Does anyone recognize this ?

[Brian Kardell]

Brian Kardell :: @bkardell :: hitchjs.com
On Oct 17, 2012 8:28 AM, Philippe Wittenbergh e...@l-c-n.com wrote:


 In a stylesheet that I’ve temporarily inherited I see multiple times the
 following code (and the stylesheet is otherwise reasonably well written):

 E {
 display: inline-block;
 float: left;
 /* .. more .. */
 }

 Afaict, those are all applied to inline elements, no width is specified.
 On the face of it, that code is completely non-sensical (float will make
 the element display: block anyway – CSS 2.1:9.7 [1]).

 The question: does anyone recognizes this as some kind of hack for
 whatever browser ? I wouldn’t know what the benefit is, though.

 [1] http://www.w3.org/TR/CSS21/visuren.html#dis-pos-flo


 Philippe
 --
 Philippe Wittenbergh
 http://l-c-n.com




 __
 css-discuss [css-d@lists.css-discuss.org]
 http://www.css-discuss.org/mailman/listinfo/css-d
 List wiki/FAQ -- http://css-discuss.incutio.com/
 List policies -- http://css-discuss.org/policies.html
 Supported by evolt.org -- http://www.evolt.org/help_support_evolt/

__
css-discuss [css-d@lists.css-discuss.org]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
List policies -- http://css-discuss.org/policies.html
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/

Re: [css-d] Does anyone recognize this ?

[Brian Kardell]

On Oct 17, 2012 8:28 AM, Philippe Wittenbergh e...@l-c-n.com wrote:


 In a stylesheet that I’ve temporarily inherited I see multiple times the
following code (and the stylesheet is otherwise reasonably well written):

 E {
 display: inline-block;
 float: left;
 /* .. more .. */
 }

 Afaict, those are all applied to inline elements, no width is specified.
On the face of it, that code is completely non-sensical (float will make
the element display: block anyway – CSS 2.1:9.7 [1]).

 The question: does anyone recognizes this as some kind of hack for
whatever browser ? I wouldn’t know what the benefit is, though.

 [1] http://www.w3.org/TR/CSS21/visuren.html#dis-pos-flo


 Philippe
 --
 Philippe Wittenbergh
 http://l-c-n.com




 __
 css-discuss [css-d@lists.css-discuss.org]
 http://www.css-discuss.org/mailman/listinfo/css-d
 List wiki/FAQ -- http://css-discuss.incutio.com/
 List policies -- http://css-discuss.org/policies.html
 Supported by evolt.org -- http://www.evolt.org/help_support_evolt/

I am not necessarily suggesting that this is the case, but it isn't
necessarily a mistake...depending on the rest of the rules, a designer may
have set that up knowing exactly that and then merely selectively twiddle
float in more specific/later rules.

Brian Kardell :: @bkardell :: hitchjs.com
__
css-discuss [css-d@lists.css-discuss.org]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
List policies -- http://css-discuss.org/policies.html
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/

[css-d] Help finding history/discussion on multiple values

[Brian Kardell]

I've spent a lot of time searching through the archives, reading through
searching online looking for any of the discussions and rationale that led
to the multiple comma separated lists values allowed by a few of the modules
now like backgrounds and transitions.  It raises a lot of questions for me
that I'm having a hard time resolving by just reading the spec... Does
anyone know where I can find some background information on this?
__
css-discuss [css-d@lists.css-discuss.org]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
List policies -- http://css-discuss.org/policies.html
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/

Re: [css-d] Help finding history/discussion on multiple values

[Brian Kardell]

Sorry Gabriel, perhaps I should have been more specific.  You example shows
commas being used to separate values being passed to a function which
resolves a clipping region - this seems pretty standard and intuitive...

On the other hand - what I am talking about is modules (like background or
transition) whose values can be multiple (not expressed in shorthand, but
actually multiple) to reflect something like multiple layers of a background
- as described (again, for example) here:
http://www.w3.org/TR/css3-background/#layering


background-image: url(flower.png), url(ball.png), url(grass.png);
background-position: center center, 20% 80%, top left, bottom right;
background-origin: border-box, content-box;
background-repeat: no-repeat;


This means that a particular element has more than one value for a module
property - which isn't generally the case prior to this in CSS.  A serious
distinction between your example and mine is that given that your example is
merely providing values to a function its meaning is generally pretty
obvious with or without the commas and its impact is very contained.  There
is really nothing in or about CSS that would lead me to believe that I could
override the third argument somehow (definitely correct me if I am wrong
about that) - however, overriding individual properties with via a rule with
greater specificity or processed later is exactly the sort of thing that CSS
has been designed to do since day 1 when it comes to my case - and I don't
see how this allows it.  Given the array-like nature - CSS has no (to the
best of my knowledge) good way of dealing with those kinds of things that
would seem to be common... As far as I can tell, you wouldn't be able to
create a rule which added a new layer, nor a way to identify the right layer
in an array/list to override a property on.  There is also potentially some
disagreement and lack of clarity in terms of how properties will balance in
there... The drafts still have lots of red comments and I've seen some
discussion that it might not be 100% consistent between browsers (we would
expect that for a while) or even maybe between module specifications.

I think that reading what people were thinking when this was getting drafted
would be very informative to me in trying to understand the decisions,
considerations and direction.

-Brian


On Fri, Jun 10, 2011 at 11:16 AM, Gabriele Romanato 
gabriele.roman...@gmail.com wrote:

 Hi Brian.
 The problem with CSS commas is that they're not required in all cases.
 Consider this example:

 #test {
   clip: rect(10px, 10px, 10px, 5px);
 }

 CSS specs say that for the clip property commas are optional, but some
 browsers don't allow them to appear between values, meaning that for some
 browsers they're not allowed, even though that specs say the contrary.

 This happens also for the new properties. In other words, commas are
 property-dependent, because the CSS syntax says that they can be considered
 as separators.
 With the CSS3 properties, things get more complicated with the widespread
 use of browser-specific extensions (aka vendor prefixes).

 I think that you should document yourself by reading the browser-specific
 implementations, not the specs, because the properties you mentioned are so
 far supported only via vendor prefixes.
 When browsers will implement them without prefixes, then you can go
 straight to the official CSS3 module specs and read how they actually work.

 HTH :-)

 Gabriele Romanato

 --
 http://www.css-zibaldone.com/
 http://www.css-zibaldone.com/test/ (English)
 http://www.css-zibaldone.com/articles/ (English)
 http://onwebdev.blogspot.com/  (English)


__
css-discuss [css-d@lists.css-discuss.org]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
List policies -- http://css-discuss.org/policies.html
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/

Re: [css-d] Making A Link Disappear When Revisited By A Reader

[Brian Kardell]

Could you not use visited?

a:visited{
display:none;
}

On Fri, Jun 10, 2011 at 2:27 PM, Fabienne i...@possets.com wrote:


 I am writing a novelette and want to have two endings to the story. I also
 want to have the reader choose one answer and not be able to go back and
 read the one they did not choose later. So I want the link to the ending
 they did not choose disappear after they make their choice. How would I go
 about doing that with CSS, or could I?

 I have thought of having a page they go to to make their initial choice,
 then they would go to the page for the ending they chose which would have a
 link back to the choice page BUT that page would have only the link to the
 one they chose and the one they did not choose would be gone (because the
 page to go back to would be another page, really).

 I hope I explained it sufficiently. It's a simple concept, I just want the
 reader to make up their mind and not be able to go back to read the other
 ending. Thanks for any inputs on this. I am afraid I am stumped. _
 _ _-- _
 Fabienne
 __
 css-discuss [css-d@lists.css-discuss.org]
 http://www.css-discuss.org/mailman/listinfo/css-d
 List wiki/FAQ -- http://css-discuss.incutio.com/
 List policies -- http://css-discuss.org/policies.html
 Supported by evolt.org -- http://www.evolt.org/help_support_evolt/

__
css-discuss [css-d@lists.css-discuss.org]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
List policies -- http://css-discuss.org/policies.html
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/

Re: [css-d] Making A Link Disappear When Revisited By A Reader

[Brian Kardell]

Oh I see - I think I misread... Sorry :)  But yes, I think the idea would
still be to use visited somehow.  I don't think that what is described here
would necessarily work though - would it? I mean, if the one clicked were on
the right, it wouldn't really have any visible impact (it would just grow
out of the viewable area and be clipped).  I think you would have to also
position it and lay it on a higher layer to hide it.

On Fri, Jun 10, 2011 at 2:44 PM, Chris Blake ch...@3pointdesign.com wrote:

 Hi,

 Just an idea, but might be a bit far fetched:

 The link you don't want needs to be visible at the start, and then after
 another link is clicked to disappear. I think that if both links were in a
 div with a set width and height you could change the CSS for the 'visited'
 link to increase in size, and sort of knock the other link out of sight.

 for example a 200px wide container containing to block links at 100px wide
 each. Once one link has been visited it becomes 200px wide, pushing the
 other link into overflow hidden and like magic, it's gone.

 does that make sense?

 BR, CB



 On 11/06/2011, at 2:32 AM, i...@ecoitsf.com wrote:

  Choose your own adventure. Cool.

 Sincerely,

 Matthew P. Johnson
 415.254.1563
 Eco I.T.
 ecoitsf.com

 - Reply message -
 From: Fabienne i...@possets.com
 Date: Fri, Jun 10, 2011 11:27 am
 Subject: [css-d] Making A Link Disappear When Revisited By A Reader
 To: css-d@lists.css-discuss.org


 I am writing a novelette and want to have two endings to the story. I
 also want to have the reader choose one answer and not be able to go
 back and read the one they did not choose later. So I want the link to
 the ending they did not choose disappear after they make their choice.
 How would I go about doing that with CSS, or could I?

 I have thought of having a page they go to to make their initial choice,
 then they would go to the page for the ending they chose which would
 have a link back to the choice page BUT that page would have only the
 link to the one they chose and the one they did not choose would be gone
 (because the page to go back to would be another page, really).

 I hope I explained it sufficiently. It's a simple concept, I just want
 the reader to make up their mind and not be able to go back to read the
 other ending. Thanks for any inputs on this. I am afraid I am stumped. _
 _ _-- _
 Fabienne
 __
 css-discuss [css-d@lists.css-discuss.org]
 http://www.css-discuss.org/mailman/listinfo/css-d
 List wiki/FAQ -- http://css-discuss.incutio.com/
 List policies -- http://css-discuss.org/policies.html
 Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
 __
 css-discuss [css-d@lists.css-discuss.org]
 http://www.css-discuss.org/mailman/listinfo/css-d
 List wiki/FAQ -- http://css-discuss.incutio.com/
 List policies -- http://css-discuss.org/policies.html
 Supported by evolt.org -- http://www.evolt.org/help_support_evolt/


 __
 css-discuss [css-d@lists.css-discuss.org]
 http://www.css-discuss.org/mailman/listinfo/css-d
 List wiki/FAQ -- http://css-discuss.incutio.com/
 List policies -- http://css-discuss.org/policies.html
 Supported by evolt.org -- http://www.evolt.org/help_support_evolt/

__
css-discuss [css-d@lists.css-discuss.org]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
List policies -- http://css-discuss.org/policies.html
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/

Re: [css-d] Making A Link Disappear When Revisited By A Reader

[Brian Kardell]

I don't see how a cookie changes it a lot... Generally speaking, aren't
things visited as long as they are in the cache?  Neither one goes across
actual browsers (like FF to IE or Chrome)... You'd need a database/login for
that kind of guarantee - but I get the impression that he's merely looking
for something simple to visually keep track of it while a user is on the
page or maybe even next time someone comes back.  He should be able to
accomplish that with :visited ... I just misunderstood which one he wanted
to hide.



On Fri, Jun 10, 2011 at 2:54 PM, Tim Climis tim.cli...@gmail.com wrote:

 On Friday, June 10, 2011 2:37:38 pm Brian Kardell wrote:
  Could you not use visited?
 
  a:visited{
  display:none;
  }
 

 No.  that would be the exact opposite of what the OP wants.  that would
 make
 the ending the reader chose inaccessible (and after choosing both endings,
 *all* endings inaccessible).

 Personally, I don't think CSS is the correct solution for this -- to work
 effectively, it would have to remember across browser sessions, meaning a
 cookie or something.  I'd be doing this in the server-side language that
 builds the page.  If no link chosen, display both, and then make a record
 of
 which was chosen, stored either on your server, or on the reader's
 computer.
 And then check that file on the next page visit, to display the proper
 link.

 ---Tim
 __
 css-discuss [css-d@lists.css-discuss.org]
 http://www.css-discuss.org/mailman/listinfo/css-d
 List wiki/FAQ -- http://css-discuss.incutio.com/
 List policies -- http://css-discuss.org/policies.html
 Supported by evolt.org -- http://www.evolt.org/help_support_evolt/

__
css-discuss [css-d@lists.css-discuss.org]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
List policies -- http://css-discuss.org/policies.html
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/

Re: [css-d] Making A Link Disappear When Revisited By A Reader

[Brian Kardell]

I believe mark is right with regard to the possibikity of that being ignored
by newer browsers.  Wow, that's good to know.
On Jun 10, 2011 4:28 PM, G.Sørtun gunla...@c2i.net wrote:
 On 10.06.2011 20:27, Fabienne wrote:
 So I want the link to the ending they did not choose disappear after
 they make their choice.

 You can use relative or absolute positioned links, and modify position
 and z-index to layer the visited link on top of the non-visited link.
 That way only the chosen link will be visible and available.

 regards
 Georg

 __
 css-discuss [css-d@lists.css-discuss.org]
 http://www.css-discuss.org/mailman/listinfo/css-d
 List wiki/FAQ -- http://css-discuss.incutio.com/
 List policies -- http://css-discuss.org/policies.html
 Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
__
css-discuss [css-d@lists.css-discuss.org]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
List policies -- http://css-discuss.org/policies.html
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/