Open
Bug 164685
Opened 22 years ago
Updated 2 years ago
Don't add ="" to custom boolean attributes
Categories
(Core :: DOM: Serializers, defect)
Tracking
()
NEW
People
(Reporter: chris.weaver, Unassigned)
Details
(Keywords: testcase)
Attachments
(1 file)
226 bytes,
text/html
|
Details |
We use Maxum's NetCloak Pro [ http://www.maxum.com/NetCloak/ ] on our webserver (G4 tower, OS X Server Unlimited running Apache). To call up a server-side macro from NetCloak's macro file, one uses a <macro> tag as such: <macro stylesheet> In most other editors I use or have tried (DreamWeaver, PageSpinner, GoLive, Freeway) these <macro> tags are ignored, since they are interpreted server-side. In Mozilla's Composer, however, these tags (from a standard template we distribute widely) are converted as below: <macro stylesheet=""></macro> Obviously, NetCloak doesn't like this syntax and fails to use the <macro> correctly. Is there any way to turn off Mozilla's syntax checking/rearrangement, per tag? Thanks.
Confirmed using FizzillaCFM/1.1-final on 10.1.5. Reassigning to Editor: Core.
Assignee: syd → kin
Status: UNCONFIRMED → NEW
Component: Editor: Composer → Editor: Core
Ever confirmed: true
Summary: Using NetCloak Macro tags in Composer → Don't add ="" to custom boolean attributes
Composer adds ="" to the stylesheet boolean attribute in this testcase.
glazman, are we doing this internally? Or is this happening in the serializer?
Assignee: kin → glazman
The parser handles boolean attributes in shorthand form only in the html namespace for the time being. Fixing this bug would require adding to the parser the ability to declare an attribute as boolean whatever is namespace, and the implementation boolean attributes. Since boolean attributes in shorthand form don't exist in XML, and since user-defined elements/attributes are not supposed to be in a document at browsing time, I am not sure we're going to fix this... Kin, what do you think ?
Comment 5•22 years ago
|
||
I thought the appropriate thing to output for booleans was something like foo="foo"; this sounds like a duplicate bug but perhaps I misunderstand?
Updated•17 years ago
|
QA Contact: sujay → editor
Comment 6•2 years ago
|
||
The bug assignee is inactive on Bugzilla, so the assignee is being reset.
Assignee: daniel → nobody
Comment 7•2 years ago
|
||
I think that it's no problem to add =""
, but I don't find any standards about serialization of boolean attributes. Anyway, this must be handled by serializer's staff.
Component: DOM: Editor → DOM: Serializers
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•