Closed Bug 670512 Opened 13 years ago Closed 4 years ago

XUL: Document the disableonsend attribute

Categories

(Developer Documentation Graveyard :: Mozilla Platform, defect, P5)

All
Other
defect

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: tessarakt, Unassigned, Mentored)

Details

(Keywords: good-first-bug, helpwanted, Whiteboard: [lang=html])

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:7.0a2) Gecko/20110709 Firefox/7.0a2
Build ID: 20110709042004

Steps to reproduce:

I was looking for documentation of the "disableonsend" attribute, which occured in addon code I am currently having a closer look at.



Actual results:

There is such documentation on MDN. Nothing found via Google, no page at https://developer.mozilla.org/en/XUL/Attribute/disableonsend .


Expected results:

The attribute seems to exist. It does not occur only in the addon, but also in Mozilla code, see bug 509209. So there should be documentation.
It's just a custom attribute used by the messagecompose window. I'd put it in Thunderbird specific documentation, and not under XUL attributes.
Is there already documentation where this would fit? IMO, there should be documentation for XUL document of Thunderbird about what has to be observed when creating an overlay for it.
I suggest that you get on IRC and connect to irc://moznet/maildev (this is the maildev channel on the mozdev IRC server). There should be people there who can suggest the proper place to place such documentation.
<sid0> tessarakt2: see https://mxr.mozilla.org/comm-central/search?find=%2F&string=disableonsend
<sid0> seems like it's a custom attribute used by our compose code
<tessarakt2> yeah
<tessarakt2> is there documentation on what you have to care about when writing a XUL overlay?
<tessarakt2> (i.e., an overlay for a specific window)
<tessarakt2> or should there be such documentation?
<sid0> well, this is custom and highly specific
<sid0> there probably should be documentation for this
<sid0> and this is like a lot of other custom attributes we probably define
<tessarakt2> I guess if you leave it out, something will break
Component: Documentation Requests → Documentation
Component: Documentation → General
Product: Mozilla Developer Network → Developer Documentation
This should actually be documented right in the XUL reference, but flagged as Thunderbird specific.
Component: General → Mozilla Platform
Whiteboard: u=mozdev p=1
Whiteboard: u=mozdev p=1 → u=mozdev p=1 c=Platform
XUL is going away. No Staff Writer will ever work on this.

We will still accept contributed documentation though: reopen only if you start documenting it.
Status: UNCONFIRMED → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
(In reply to Jean-Yves Perrier [:teoli] from comment #6)
> XUL is going away. No Staff Writer will ever work on this.
> 
> We will still accept contributed documentation though: reopen only if you
> start documenting it.
Nobody is going to contribute to a bug that is marked WONTFIX.
I'm setting this as a GFB so that bugsahoy can pick this up.
http://www.joshmatthews.net/bugsahoy/
Mentor: blog, vseerror, philip.chee
Status: RESOLVED → REOPENED
Ever confirmed: true
Keywords: helpwanted
Resolution: WONTFIX → ---
Whiteboard: u=mozdev p=1 c=Platform → [good first bug][lang=html]
hi. I would like to contribute to the documentation. Since it is my maiden attempt towards the documentation bugs, I request you to help me getting started.
Hello,

I would like to work on this bug.

hello, please can someone assign the project to me, I would like to work on it, I am an applicant of outreachy program. thank you.

The MDN team is no longer actively working on Mozilla Platform docs. Volunteer contributions are welcome.

Priority: -- → P5
Keywords: good-first-bug
Whiteboard: [good first bug][lang=html] → [lang=html]
MDN Web Docs' bug reporting has now moved to GitHub. From now on, please file content bugs at https://github.com/mdn/sprints/issues/ and platform bugs at https://github.com/mdn/kuma/issues/.
Status: REOPENED → RESOLVED
Closed: 9 years ago4 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.