Re: [whatwg] font (was Support Existing Content)
Adrian Sutton wrote: That said, by default our editor outputs the span tag version because we like to follow standards and I recommend using our styles menu to apply CSS classes and appropriate structural markup (headings etc). We did however have to go back and add an option to output font tags because of user complaints. Why did these user complaints arise? How did the end-users tell the difference between the span and font elements? -- Benjamin Hawkes-Lewis
Re: [whatwg] font (was Support Existing Content)
On 2/5/07 4:59 PM, Benjamin Hawkes-Lewis [EMAIL PROTECTED] wrote: Adrian Sutton wrote: That said, by default our editor outputs the span tag version because we like to follow standards and I recommend using our styles menu to apply CSS classes and appropriate structural markup (headings etc). We did however have to go back and add an option to output font tags because of user complaints. Why did these user complaints arise? How did the end-users tell the difference between the span and font elements? They had backend systems that didn't support CSS. Like PDF conversion utilities etc. Benjamin Hawkes-Lewis Regards, Adrian Sutton. __ Adrian Sutton, Integrations Product Manager Global Direct: +1 (650) 292 9659 x717 Australia: +61 (7) 3858 0118 UK +44 (20) 8123 0617 x717Mobile +61 (4) 222-36329 Ephox http://www.ephox.com/, Ephox Blogs http://planet.ephox.com/
Re: [whatwg] additional empty elements
On 1 May 2007, at 20:21, Brenton Strine wrote:
However, if I then wanted to add additional special
styling to the first and third div, (e.g.. a border and
background color) it is less graceful. I could add style
attributes, but that would be wasteful if I want to do
this on a large scale. Multiple classes would be
confusing.
A nice solution would be the addition of a few div tags.
(e.g. div2, div3, div4 and div5.) Then you could
do something like this:
style
div1 {text-indent:0px;}
div2 {text-indent:10px;}
div3 {text-indent:20px;}
/style
Why not:
!DOCTYPE html
style
.first {
color: red;
}
.first + div {
text-indent: 10px;
}
.first + div + div {
text-indent: 20px;
color: blue;
}
/style
div class=firstIndent 0/div
divIndent 1/div
divIndent 2/div
div class=firstIndent 0/div
divIndent 1/div
divIndent 2/div
Re: [whatwg] font
At 11:01 +1000 UTC, on 2007-05-02, Adrian Sutton wrote: On 2/5/07 1:28 AM, Sander Tekelenburg [EMAIL PROTECTED] wrote: [...] can you explain exactly how span is much more difficult to work with, and for whom? Quite a number of the cheap HTML to PDF conversion processes don't support CSS. Additionally, syndicated HTML (via Atom, RSS etc) tends to have inline CSS removed because of cross site scripting vulnerabilities (you can embed JavaScript in CSS and at least IE will execute it). OK. Real world issues. But that doesn't mean that the HTML spec is the place to fix those. Looks more like an opportunity for beter PDF generators to grab market share and for IE to fix security bugs. [...] Some people do restrict the editor to just applying predefined CSS classes and as a result they get a very consistent, easy to maintain site. Most however, prefer having the flexibility of a font menu so they can apply the specific font they won't precisely when they want it. OK. Too bad. Still, I don't see why this would warrant making font conforming. [...] People want the editor to look and work like Microsoft Word and Word has a font menu. Right. Given that that is what they're used to that's understandable. However used to implies that the same people could work with a more semantic editor, if they'd be used to that. People get born every day without yet being used to Word. -- Sander Tekelenburg The Web Repair Initiative: http://webrepair.org/
Re: [whatwg] Cue points in media elements
At 17:04 -0400 1/05/07, Brian Campbell wrote: On May 1, 2007, at 1:05 PM, Kevin Calhoun wrote: I believe that a cue point is reached if its time is traversed during playback. What does traversed mean in terms of (a) seeking across the cue point (b) playing in reverse (rewinding) and (c) the media stalling an restarting at a later point in the stream? I would say that playing (at any rate and in any direction) is a continuous function, and therefore cue points are triggered, when playing, whenever two samples of the time straddle the cue point (where straddel includes one of the samples being at the cue point). Seeking is discontinuous, and therefore cue points are triggered only if a seek results in landing on the cue point, if not playing. If playing, then the usual rules apply. Frame dropping, stalling, and so on, are aspects of the playback behavior and nothing to do with the logical model of cues laid on a time axis. -- David Singer Apple Computer/QuickTime
