Ian Hickson wrote:
On Tue, 19 Jul 2005, Dean Edwards wrote:
The point is, I can do all sorts of things using script. Alter styles,
create elements etc. But when I switch media, I have no programmatic way
to alter those effects. Please specify I means to do this.
You don't switch media.
Dean Edwards wrote:
OK, we don't switch media. But when I press print or invoke the print
method, a copy of the DOM is sent to the printer. If I have altered the
DOM by adding elements or by changing the style property then I would
like to be able to undo those changes before my DOM goes to
Matthew Raymond wrote:
Dean Edwards wrote:
OK, we don't switch media. But when I press print or invoke the print
method, a copy of the DOM is sent to the printer. If I have altered the
DOM by adding elements or by changing the style property then I would
like to be able to undo those changes
Kornel Lesinski wrote:
style attribute is supposed to have cascade value like ID selector.
No, style attributes override everything. See
http://www.w3.org/TR/CSS21/cascade.html#specificity
smime.p7s
Description: S/MIME Cryptographic Signature
Matthew Raymond wrote:
I know this isn't how you meant it, but this all seems a bit user
hostile. The user sees something on the screen he/she wants to print,
but an event is called at the last minute that changes the content to
something else
You can already do that with CSS...
@media
Sjoerd Visscher wrote:
Matthew Raymond wrote:
I know this isn't how you meant it, but this all seems a bit user
hostile. The user sees something on the screen he/she wants to print,
but an event is called at the last minute that changes the content to
something else before the user can print.
Quoting Matthew Raymond [EMAIL PROTECTED]:
You can do that with css anyway, what is your point?
That CSS can be overridden by the user stylesheet?
Userbase: 2. (Both are geek.)
--
Anne van Kesteren
http://annevankesteren.nl/
On Tue, 19 Jul 2005, Dimitri Glazkov wrote:
No, I don't believe that is always the case. The user _sometimes_ wants
to print what he/she sees, but my experience tells me that most of the
time, the user wants to print what is considered main content of the
page. For example, I am using my
On 7/19/05, Ian Hickson [EMAIL PROTECTED] wrote:
@media {
navigation { display: none; }
}
Ok, at least we all agree that it's not what the user sees :)
What functionality are you lacking? (Both in screen and print.)
Like, adding contextual content for print. Just like your main content
Ian Hickson wrote:
What functionality are you lacking? (Both in screen and print.)
Suppose I want to add inprint links' full urls in parenteses after
links' text. In CSS I can do;
a[href]:after {
content: attr(href);
}
But it's not enough since href may contain unresolved URL and I want
Dimitri Glazkov wrote:
On 7/19/05, Ian Hickson [EMAIL PROTECTED] wrote:
What functionality are you lacking? (Both in screen and print.)
Like, adding contextual content for print. Just like your main content
is not the only thing on the page, same may hold true for the
On Tue, 19 Jul 2005, Dimitri Glazkov wrote:
a) my invoice format requires a timestamp that says something like this:
printed by [person] on [timestamp].
This use case is being dealt with in the CSS paged media and CSS generated
content specifications.
b) To capture the essence of the
On Tue, 19 Jul 2005, Maniac wrote:
Suppose I want to add inprint links' full urls in parenteses after
links' text. In CSS I can do;
a[href]:after {
content: attr(href);
}
But it's not enough since href may contain unresolved URL and I want
them full.
That's a use case for a new
Ian Hickson wrote:
That's a use case for a new feature in CSS, not in HTML. :-)
It is solvable with events discussed. My point is that authors
traditionally use scripting to solve things that can't be solved with
other means. It's normal.
On 7/19/05, Ian Hickson [EMAIL PROTECTED] wrote:
b) To capture the essence of the browsing session, I would like to build
a breadcrumb at the bottom of the printed page, displaying titles and
urls of pages the user have visited on the site during this visit.
That seems like something that
On Tue, 19 Jul 2005, Maniac wrote:
Ian Hickson wrote:
That's a use case for a new feature in CSS, not in HTML. :-)
It is solvable with events discussed. My point is that authors
traditionally use scripting to solve things that can't be solved with
other means. It's normal.
Granted. But
On Tue, 19 Jul 2005, Dimitri Glazkov wrote:
However, I think am starting to see what you're seeing. Basically, your
approach is to provide all content in the DOM tree and then flip
switches as needed to present it to various media types. Right?
Right.
Essentially, you are creating
Jim Ley wrote:
This is flawed though, as it requires all the content to be in the
page, including media-specific content. CSS cannot remove content, CSS
is optional, consider:
This page span id=viewedviewed/spanspan
id=printedprinted/span on ...
This is a contrived example of how people
Btw, in HTML5 class name handling is easier through the DOMTokenString
interface, you just write:
element.classNames.add(somethingThatIsOnlyVisibleOnScreen)
/olav
Dean Edwards wrote:
If I set element.style.display = block how do I hide it using a style
sheet when it is printed?
I dont think you should set element.style.display to block, if the
element should be visible only on screen and not in print. It would be
better to dynamically assign it a
On 7/18/05, Ian Hickson [EMAIL PROTECTED] wrote:
Why would you suspend a timer?
(And why would the UA not suspend the timers itself?)
You're saying that when a user print's an HTML5 user agent MUST stop
all setTimeout counters, I don't see that in the spec, nor why it
would be an expectation of
Olav Junker Kjær wrote:
Dean Edwards wrote:
IE has some nice onbeforeprint/onafterprint events. Can we add these too?
Arent these event mostly used to transform the view before printing it?
I think this is better handled by a print-specific style-sheet today.
If I set
Jim Ley wrote:
On 7/18/05, Ian Hickson [EMAIL PROTECTED] wrote:
Why would you suspend a timer?
(And why would the UA not suspend the timers itself?)
You're saying that when a user print's an HTML5 user agent MUST stop
all setTimeout counters, I don't see that in the spec, nor why it
would be
On 7/19/05, Matthew Raymond [EMAIL PROTECTED] wrote:
Jim Ley wrote:
You're saying that when a user print's an HTML5 user agent MUST stop
all setTimeout counters, I don't see that in the spec, nor why it
would be an expectation of a scripter.
So wait, we need to add new events because
Ian Hickson wrote:
On Mon, 18 Jul 2005, Dean Edwards wrote:
OK. Forget CSS for a moment (although this is still a consideration for
me). What if I want to suspend a timer while the page is being printed?
Printing is (supposedly) instantaneous. Why would you suspend a timer?
(And why would
Matthew Raymond wrote:
The common use of onbeforeprint/onafterprint is to add content to a
document that is only relevant to printed media, this is something
that cannot be done with CSS, since CSS is optional, so if we just
hide content with CSS, we're stuck with the situation that users
On Tue, 19 Jul 2005, Dean Edwards wrote:
Ian Hickson wrote:
On Mon, 18 Jul 2005, Dean Edwards wrote:
OK. Forget CSS for a moment (although this is still a consideration
for me). What if I want to suspend a timer while the page is being
printed?
Printing is (supposedly)
On Tue, 19 Jul 2005, Dean Edwards wrote:
The point is, I can do all sorts of things using script. Alter styles,
create elements etc. But when I switch media, I have no programmatic way
to alter those effects. Please specify I means to do this.
You don't switch media. It's quite possible to
Shouldn't the print method on the window DOM interface be defined as well?
Example: button onclick=window.print()print/button
--
Anne van Kesteren
http://annevankesteren.nl/
On Sun, 17 Jul 2005, Anne van Kesteren wrote:
Shouldn't the print method on the window DOM interface be defined as well?
Example: button onclick=window.print()print/button
It's probably best not to review the spec for missing features before the
first call for comments. The spec at the
30 matches
Mail list logo