Re: [css-d] background image rendering issue - a safari bug for iPad or CSS ?

On Jun 11, 2011, at 10:42 AM, tee wrote: > Still I have one question: you mentioned 100% for outer divs are not > necessary - but this is what I thought how iOS Safari "downsize" works, that > it shrinks everything inside the 100% to viewport size, meaning the 100% > width for outer box is th

Re: [css-d] background image rendering issue - a safari bug for iPad or CSS ?

Philipe, Thank you. > > And that is exactly how CSS is designed to work. You outer boxes (static, > inflow boxes) are as wide as the viewport, OK, I fully get it now. This is the first layout I ever did that goes beyond 980px (thus the cut off part is not something I saw before in iPad/iPhon

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

At 2:27 PM -0400 6/10/11, Fabienne 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 af

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

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 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 choi

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

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 chos

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

On Fri, Jun 10, 2011 at 14:54, Brian Kardell wrote: > 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 righ

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

Brian has made a good point, a link on the right would expand out of view, even if it was the one you want to remain. However he's indicated using z-index too which with the right CSS tweeks could hide the unwanted link out of sight. On 11/06/2011, at 2:54 AM, Brian Kardell wrote: Oh I

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

That seems like the logical thing to do but it's actually the opposite of what I want to happen. I want the non visited one to disappear when they return to the page from which they choose. Somehow I can't figure out how to do that. ---Fabienne On 6/10/2011 2:37 PM, Brian Kardell wrote: Could

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

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

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

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 i

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

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 gro

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

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

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

Could you not use visited? a:visited{ display:none; } On Fri, Jun 10, 2011 at 2:27 PM, Fabienne 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

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

Choose your own adventure. Cool. Sincerely, Matthew P. Johnson 415.254.1563 Eco I.T. ecoitsf.com - Reply message - From: "Fabienne" Date: Fri, Jun 10, 2011 11:27 am Subject: [css-d] Making A Link Disappear When Revisited By A Reader To: I am writing a novelette and want to have tw

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

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

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

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 tran

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

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 b

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

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

Re: [css-d] IE 7 z-index issue

>> Well if you think you are confused Tom, try spinning some pinwheels in my >> twisted little mind... >> What say we try this [if nothing else its entertaining] and see of IE 7 goes >> along with the program on your end? >> >> html >> >> > > I got to this

Re: [css-d] IE 7 z-index issue

> Well if you think you are confused Tom, try spinning some pinwheels in my > twisted little mind... > What say we try this [if nothing else its entertaining] and see of IE 7 goes > along with the program on your end? > > html > > css > header{position: rel

Re: [css-d] Popout box

On Jun 10, 2011, at 8:28 AM, Nazish wrote: > I'd like to create a popout box... Project 7 has a product called Tooltip Magic that quite impresses me. http://www.projectseven.com/products/tools/tooltips/index.htm Chuck M __

[css-d] Popout box

Hi everyone, I'd like to create a popout box for a list of products in my table. For example, when the user's mouse hovers over a cell, the popout box with more info will display, and the popout box will disappear when the mouse is not hovering on the cell. The Netflix website is a great example o