Closed
Bug 817589
Opened 12 years ago
Closed 12 years ago
move mozAudioChannelType to a separated interface
Categories
(Core :: DOM: Core & HTML, defect)
Core
DOM: Core & HTML
Tracking
()
RESOLVED
INVALID
People
(Reporter: baku, Assigned: baku)
References
Details
Attachments
(1 file)
16.14 KB,
patch
|
Details | Diff | Splinter Review |
We don't want to change the nsIDOMHTMLMediaElement interface so we are proposing to move any audio channel related thing to a separated interface called nsITMLMediaElement2. This new interface should be enabled only for b2g.
Assignee | ||
Comment 1•12 years ago
|
||
Attachment #687770 -
Flags: review?(jonas)
![]() |
||
Comment 2•12 years ago
|
||
> We don't want to change the nsIDOMHTMLMediaElement interface
Is this just because you want the new properties to be pref-controlled, or is there something else going on?
Assignee | ||
Comment 3•12 years ago
|
||
https://bugzilla.mozilla.org/show_bug.cgi?id=795237#c64
Smaug proposed this approach instead changing the mediaelement interface.
Assignee | ||
Updated•12 years ago
|
Assignee: nobody → amarchesini
Assignee | ||
Updated•12 years ago
|
OS: Linux → All
Hardware: x86_64 → All
![]() |
||
Comment 4•12 years ago
|
||
Oh, for beta, sure. I'm more interested in what happens on trunk going forward; on beta we just do the separate interface.
Specifically, I'm interested in what happens when we stop using XPConnect for media elements and start using WebIDL, at which point the separate-interface thing will be pretty pointless on its own.
Assignee | ||
Comment 5•12 years ago
|
||
We can merge these 2 interfaces in future before migrating to webIDL.
This property was added to nsIHTMLMediaElement in aurora, so *removing* it would actually be what would causing a change at this point. So I think we should keep things as they are.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → INVALID
Attachment #687770 -
Flags: review?(jonas)
Comment 7•12 years ago
|
||
(In reply to Jonas Sicking (:sicking) from comment #6)
> This property was added to nsIHTMLMediaElement in aurora, so *removing* it
> would actually be what would causing a change at this point. So I think we
> should keep things as they are.
I thought the stuff would land to beta, where we must not change any interfaces.
(If needs-to-land-to-beta is not the case, I have no idea what b2g stuff lands where and when :) )
Comment 8•12 years ago
|
||
Oh, sorry, if it landed already in Aurora, it obviously isn't landing to beta, because it is already there.
I was looking at some patch which was making changes to .idl file and which would be landing to
beta, I guess Bug 805333, but that was about onfoo properties.
My mistake, sorry.
Updated•6 years ago
|
Component: DOM → DOM: Core & HTML
You need to log in
before you can comment on or make changes to this bug.
Description
•