Just a quick thought after reading the revised adding
css to the editor document:
It would also be nice if JavaScript could ask for
permission to disable the user style sheet.
Also, how does the edior display an element with
display:none? My guess is it is viewable in tag mode
as just a tag?
-
Daniel Glazman wrote:
> Good morning,
>
> I have added yesterday evening to www.mozilla.org a new document [1]
> about basic CSS support in Composer.
Just fyi, bug 77705 [1] is a tracking bug for the CSSization of
Composer. It already contains work-in-progress code. Comments highly
welcome !
In article <[EMAIL PROTECTED]>, Daniel Glazman
<[EMAIL PROTECTED]> wrote:
> Henri Sivonen wrote:
> >> c) CSS allow visual effects that users need : first-letter,
> >> first-line,
> >
> > Again, that only works with a real block structure. If Editor doesn't
> > use real paragraphs but contin
Joe Francis wrote:
In Internet Explorer (and Microsoft Office apps by default), if you
[snip]
>
> This is one of those times where my natural inclination is to agree with
> you, but experience is telling me otherwise. If we had a selection
> model that snapped into element mode the
Daniel Glazman wrote:
>
> Good morning,
>
> I have added yesterday evening to www.mozilla.org a new document [1]
> about basic CSS support in Composer. It describes a proposal in four
> steps. All comments, suggestions and even flames welcome.
> vertical-align (replaced elements only)
Vertica
copied to mozilla-accessibility
Dreamweaver and Amaya also have nice models for selecting elements - there is
a status bar that gives the information about what the ancestors are, and a
method for selecting parent/child/sibling.
In terms of accessible editing this is important (it is one of the
Charles McCathieNevile wrote:
>
> No, the problem is that editor produces stuff that has all over the
> place, so that it works well with old mail clients. This stuff will have lots
> of first lines/first-letters (I think - should check the spec) that the
> author probably doesn't mean to selec
On Fri, 2 Mar 2001, Daniel Glazman wrote:
Henri Sivonen wrote:
>> c) CSS allow visual effects that users need : first-letter, first-line,
>
> Again, that only works with a real block structure. If Editor doesn't
> use real paragraphs but continues to use forced line breaks, things lik
Henri Sivonen wrote:
>> c) CSS allow visual effects that users need : first-letter, first-line,
>
> Again, that only works with a real block structure. If Editor doesn't
> use real paragraphs but continues to use forced line breaks, things like
> first-letter and first-line are useless for p
In article <[EMAIL PROTECTED]>, Daniel Glazman
<[EMAIL PROTECTED]> wrote:
> a) CSS allow a much better control of the rendering with media independance.
>It is possible with one structure to have multiple views on multiple
>devices as different as screen, printer, cell phone, PDA, tty,
>>> In Internet Explorer (and Microsoft Office apps by default), if you
>>> select across a word boundary, you automatically select the entire
>>> word. [MT]
>> Someone at Microsoft must have thought that was pretty odd behavior,
>> because in IE 5 for mac (which came after the win version), yo
Joe Francis wrote:
> Why can't we just continue to abuse html (without css) for these rich
> text clients? It's actually a lot easier to get it right, to get
> smaller implementations, to get faster implementations, and to get
> backwards compatibility. What I don't understand is what css b
>> I keep being told that the world implied by number 2) above is coming,
>> so we better be able to support it. But I don't understand *why* it's
>> coming. And I'm not sure I believe that it *is* coming. [JF]
> It is coming for sure. It is coming because more than 50% of american
> citizens
> > > Yes, but people who only care about the rendering and not about the
> > > structure won't be using Mozilla Composer. [MT]
> > Why is that? Composer is free, it's part of a product that is very
> > visible, it's on their platform, and it is targeted (at the moment at
> > least) right at th
In article <[EMAIL PROTECTED]>, fantasai
<[EMAIL PROTECTED]> wrote:
> If you select an element (as either part of your selection
> or your entire selection),
Just a side note wrt. block selection:
Word and such don't support the concept on nesting blocks like HTML.
Mathematica, however, do
In article <[EMAIL PROTECTED]>, Daniel Glazman
<[EMAIL PROTECTED]> wrote:
> Henri Sivonen wrote:
> Wysiwyg editing. There is not a single html editor on the market using
> html as its internal format and able to do real wysiwyg editing.
Trying to use HTML+CSS as an encoding format for font pr
Joe Francis wrote in ghost article :
> CSS is just a nightmare for wysiwyg editing, as far as I can see.
Hey Joe, thanks for the support ;- You know that I agree 100%.
> So there are two ways to go:
>
> 1) Make a css editor that is the sticky gooey dream of most of the
> leadership her
It seems that the gateway between the mozilla-editor and this newsgroup
has some holes... Joe's message is not in npm.editor but mpt's answer is.
So I remind the readers that the followup of the original message is in
the NEWSGROUP (see top of document). Don't blame me if you send to the
maili
Daniel Glazman wrote:
>
> Henri Sivonen wrote:
> >
> > Why do you suppose the author doesn't care about structure/markup?
> > If Mozilla's *Web page* editor isn't pro-intent-of-standards and
> > pro-structure, what good will it offer over the n+1 editors out
> > there that are already built aroun
Joe Francis wrote:
>
> Matthew Thomas wrote:
> >
> > In Internet Explorer (and Microsoft Office apps by default), if you
> > select across a word boundary, you automatically select the entire
> > word.
>
> Someone at Microsoft must have thought that was pretty odd behavior,
> because in IE 5 for
Daniel Glazman wrote:
| > | Why the hell are inline styles "bloated" ???
| >
| > Because the same styles are repeated (and diverged, and
| > unmaintainable) for every single document you write,
| > instead of just existing in a single file.
| >
| > This is, to a large extent, why style sh
Henri Sivonen wrote:
> Why do you suppose the author doesn't care about structure/markup? If
> Mozilla's *Web page* editor isn't pro-intent-of-standards and
> pro-structure, what good will it offer over the n+1 editors out there
> that are already built around the assumption that the user wan
Matthew Thomas wrote:
> In Internet Explorer (and Microsoft Office apps by default), if you
> select across a word boundary, you automatically select the entire word.
Someone at Microsoft must have thought that was pretty odd behavior, because
in IE 5 for mac (which came after the win version)
On Wed, 21 Feb 2001, Dylan Schiemann wrote:
[snip]
Regarding MS Word as a testcase showing that it is
better to not style selections, I could not disagree
more. Word is a painful example for how to style
documents.
Word is not such a bad example for element-based styling. But ofr inline
Daniel,
In the following text:
"This is important for compatibility with legacy
browsers that do not fully understand shorthand
properties ('border-width' for instance is a shorthand
for 'border-left-width' 'border-right-width'
'border-top-width' and 'border-bottom-width' ), with a
value between
Dylan Schiemann wrote:
> In the following text:
>
> "This is important for compatibility with legacy
> browsers that do not fully understand shorthand
> properties ('border-width' for instance is a shorthand
> for 'border-left-width' 'border-right-width'
> 'border-top-width' and 'border-bottom-
Daniel Glazman wrote:
>
> Matthew Thomas wrote:
>
> > If you regard Netscape and Outlook as `most', then yes. But Pegasus,
> > Eudora, etc just understand simple things like and -- I
> > would be extremely surprised if they ever include support for
> > `text-decoration' or `border' or whatever
Matthew Thomas wrote:
> If you regard Netscape and Outlook as `most', then yes. But Pegasus,
> Eudora, etc just understand simple things like and -- I would
> be extremely surprised if they ever include support for
> `text-decoration' or `border' or whatever.
I'd be surprised if they don't inc
Daniel Glazman wrote:
>...
> > content. And secondly, many of those mail clients which support HTML
> > (to some extent) will, in all likelihood, never support CSS. HTML
> > 3.2 will be the lingua franca.
>
> I *strongly* disagree with this last assertion but it is my personal
> opinion only. If
In article <[EMAIL PROTECTED]>, Daniel Glazman
<[EMAIL PROTECTED]> wrote:
> Matthew Thomas wrote:
> > That was my point -- it's ok to copy and paste elements across the
> > boundaries of other elements when doing mail composition (where you're
> > not concerned with counting CLASSes or specifyi
Matthew Thomas wrote:
> | This document contains a proposal for the addition of CSS 1 support to
> | the Editor. It describes the extensions the editor needs to become an
> | HTML+CSS wysiwyg editor useable by document providers writing HTML
> | documents without breaking the behavior expected b
In article <[EMAIL PROTECTED]>, Daniel Glazman
<[EMAIL PROTECTED]> wrote:
> I have added yesterday evening to www.mozilla.org a new document [1]
> about basic CSS support in Composer. It describes a proposal in four
> steps. All comments, suggestions and even flames welcome.
>
> Followup is in
Daniel Glazman wrote:
>...
> [1] http://www.mozilla.org/editor/adding-css-to-editor.html
>...
|...
| This document contains a proposal for the addition of CSS 1 support to
| the Editor. It describes the extensions the editor needs to become an
| HTML+CSS wysiwyg editor useable by document provide
Daniel Glazman wrote:
> I have added yesterday evening to www.mozilla.org a new document [1]
> about basic CSS support in Composer. It describes a proposal in four
> steps. All comments, suggestions and even flames welcome.
>
> Followup is in newsgroup netscape.public.mozilla.editor only.
>
>
Good morning,
I have added yesterday evening to www.mozilla.org a new document [1]
about basic CSS support in Composer. It describes a proposal in four
steps. All comments, suggestions and even flames welcome.
Followup is in newsgroup netscape.public.mozilla.editor only.
[1] http://www.mozilla
35 matches
Mail list logo
