Closed
Bug 203093
Opened 22 years ago
Closed 22 years ago
Move ActiveXObject --> NSActiveXObject -> GeckActiveXObject
Categories
(Core :: XPConnect, defect)
Tracking
()
VERIFIED
FIXED
People
(Reporter: arun, Assigned: dbradley)
References
Details
Attachments
(2 files)
2.03 KB,
patch
|
adamlock
:
review+
alecf
:
superreview+
sspitzer
:
approval1.4b+
|
Details | Diff | Splinter Review |
682 bytes,
patch
|
adamlock
:
review+
alecf
:
superreview+
sspitzer
:
approval1.4b+
|
Details | Diff | Splinter Review |
This is with reference to bug 203091 .
Currently, we expose certain COM properties (and programmatic component
instantiation) to the ActiveXObject object. We should instead use
NSActiveXObject since we don't purport full ActiveX support and we don't want
builds with this feature turned ON to be confused for IE.
Assignee | ||
Comment 1•22 years ago
|
||
Also consolidates the location of the strings as well.
Assignee | ||
Comment 2•22 years ago
|
||
Comment on attachment 121531 [details] [diff] [review]
Renames ActiveXObject to NSActiveXObject
Simple rename with a bit of cleanup to consolidate the strings.
Attachment #121531 -
Flags: superreview?(alecf)
Attachment #121531 -
Flags: review?(adamlock)
Comment 3•22 years ago
|
||
Comment on attachment 121531 [details] [diff] [review]
Renames ActiveXObject to NSActiveXObject
sr=alecf
Attachment #121531 -
Flags: superreview?(alecf) → superreview+
Comment on attachment 121531 [details] [diff] [review]
Renames ActiveXObject to NSActiveXObject
I'm not sure I see the point of renaming this object. We don't purport to offer
full support, yet renaming ActiveXObject is going to make the situation even
worse.
I know where the idea came from but I was under the impression that
NSActiveXObject was going to be an additional distinct object with methods to
test the availability of cids etc. And ActiveXObject was going to be left the
way it was.
Attachment #121531 -
Flags: review?(adamlock) → review-
Assignee | ||
Comment 5•22 years ago
|
||
The reasoning given was that the presence of ActiveXObject might trip up some
sniffing algorithms into thinking we're IE. I'm not a strong advocate of doing
this, so I'll let others argue for it. My reservation is that this creates
another deviation in content for people to deal with, but I got the impression
that it wouldn't be that much of a problem for content authors.
Comment 6•22 years ago
|
||
We have seen in the wild quite a bit. For example:
http://www.google.com/search?hl=en&ie=UTF-8&oe=UTF-8&q=window.ActiveXObject&btnG=Google+Search
if (window.ActiveXObject){
var xmlDoc = new ActiveXObject("Microsoft.XMLDOM");
xmlDoc.async=false; //Enforce download of XML file first. IE only.
}
else if (document.implementation && document.implementation.createDocument)
{
var xmlDoc= document.implementation.createDocument("","doc",null);
}
xmlDoc.load("myfile.xml");
If we support window.ActiveXObject then we will break on any page that contains
logic like this. Then we will hear from everyone how broken our XML support is.
This is just for one particular ActiveX object but the situation is similar for
others as well.
Up until this point we have not supported ActiveXObject. By changing that you
will see us travel down code paths in pages we have not seen before.
Comment on attachment 121531 [details] [diff] [review]
Renames ActiveXObject to NSActiveXObject
r=adamlock
Attachment #121531 -
Flags: review- → review+
Comment 8•22 years ago
|
||
*** Bug 203244 has been marked as a duplicate of this bug. ***
Assignee | ||
Comment 9•22 years ago
|
||
Comment on attachment 121531 [details] [diff] [review]
Renames ActiveXObject to NSActiveXObject
Looking for 1.4b approval. This is a simple low risk renaming of strings that
will prevent some sites confusing us for IE especially when testing for XML
parsers.
Attachment #121531 -
Flags: approval1.4b?
Comment 10•22 years ago
|
||
Comment on attachment 121531 [details] [diff] [review]
Renames ActiveXObject to NSActiveXObject
a=sspitzer
Attachment #121531 -
Flags: approval1.4b? → approval1.4b+
Assignee | ||
Comment 11•22 years ago
|
||
Patch checked in
Status: ASSIGNED → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 13•22 years ago
|
||
Reopening this bug so that we can rename it to GeckActiveXObject.
Status: VERIFIED → REOPENED
Resolution: FIXED → ---
Summary: Move ActiveXObject --> NSActiveXObject → Move ActiveXObject --> NSActiveXObject -> GeckActiveXObject
Assignee | ||
Comment 14•22 years ago
|
||
Assignee | ||
Comment 15•22 years ago
|
||
Comment on attachment 122215 [details] [diff] [review]
-> GeckActiveXObject
Simple one line string replacement NSActiveXObject -> GeckActiveXObject looking
for a quick r/sr
Attachment #122215 -
Flags: superreview?(alecf)
Attachment #122215 -
Flags: review?(adamlock)
Attachment #122215 -
Flags: review?(adamlock) → review+
Comment 16•22 years ago
|
||
Comment on attachment 122215 [details] [diff] [review]
-> GeckActiveXObject
sr=alecf
Attachment #122215 -
Flags: superreview?(alecf) → superreview+
Assignee | ||
Comment 17•22 years ago
|
||
Comment on attachment 122215 [details] [diff] [review]
-> GeckActiveXObject
Looking for 1.4b approval, this is a very simple one line string constant
change to rename to GeckActiveXObject
Attachment #122215 -
Flags: approval1.4b?
Comment 18•22 years ago
|
||
Comment on attachment 122215 [details] [diff] [review]
-> GeckActiveXObject
a=sspitzer
Attachment #122215 -
Flags: approval1.4b? → approval1.4b+
Assignee | ||
Comment 19•22 years ago
|
||
Patch checked in. (forgot to mark this fixed, patch went in around midnight last
night)
Status: REOPENED → RESOLVED
Closed: 22 years ago → 22 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•