Commit Graph

5880 Commits

Author SHA1 Message Date
Henri Sivonen
9e1fb08628 Bug 843508 - Remove support for multipart XHR responses. r=jst. 2013-03-04 11:06:15 +02:00
Mats Palmgren
b6cbb09481 Bug 690659 - Bustage fix for clang 3.2. r=Ms2ger 2013-03-03 21:34:47 +01:00
Tom Schuster
c839fd97fc Bug 690659 - Test. r=sicking 2013-03-03 19:30:13 +01:00
Tom Schuster
4fc262a11f Bug 690659 - Add the optional filename parameter to the FormData.append method. r=sicking 2013-03-03 19:30:13 +01:00
Neil Rashbrook
704cbe505f Bug 738952 Make it possible for a stream converter to propagate the actual MIME type to the document r=bz
--HG--
rename : build/mach_bootstrap.py => mach
extra : rebase_source : fdfacff52e126440966a4b989a240eb3517c29d5
2013-03-02 14:23:20 +00:00
Trevor Saunders
1a20d1b3c3 bug 845562 - remove GetFrameSelection() from nsISelectionPrivate r=smaug 2013-02-15 15:09:28 -05:00
Henri Sivonen
484e088490 Bug 844792 addendum - Adjust advice about multipart support removal in XHR and make the message non-localizable. r=smaug. 2013-03-01 16:42:39 +02:00
Boris Zbarsky
3123988ad1 Bug 845881. Go back to allowing any 2xx response code to a preflight request, since web sites do that. r=sicking 2013-03-01 00:57:13 -05:00
Boris Zbarsky
615c1738c3 Bug 776536 part 4. Turn on WebIDL bindings for NodeIterator and TreeWalker. r=peterv
The behavior here is a bit weird because Document is still not a
WebIDL object, so calling createNodeIterator or createTreeWalker via
an Xray will call the XPCOM versions of those methods.  That means
that I can't just disable XPCOM-based wrapping for TreeWalker and
NodeIterator altogether, unfortunately, which means a web page could
try stashing a TreeWalker in something like userdata and then getting
it back and end up wrapping it as an XPCOM object the second time.

I could "fix" that by adding a wrapper cache and whatnot, I guess, if
desired...  But the problem will go away once we convert Document in
any case.
2013-02-28 12:56:42 -05:00
Boris Zbarsky
0827c7c174 Bug 776536 part 3. Add a WebIDL API to NodeIterator and TreeWalker. r=peterv 2013-02-28 12:56:42 -05:00
Boris Zbarsky
d7d37d4444 Bug 776536 part 2. Rename nsTreeWalker to mozilla::dom::TreeWalker. r=peterv
--HG--
rename : content/base/src/nsTreeWalker.cpp => content/base/src/TreeWalker.cpp
rename : content/base/src/nsTreeWalker.h => content/base/src/TreeWalker.h
2013-02-28 12:56:41 -05:00
Boris Zbarsky
d46a52933e Bug 776536 part 1. Rename nsNodeIterator to mozilla::dom::NodeIterator. r=peterv
--HG--
rename : content/base/src/nsNodeIterator.cpp => content/base/src/NodeIterator.cpp
rename : content/base/src/nsNodeIterator.h => content/base/src/NodeIterator.h
2013-02-28 12:56:41 -05:00
Boris Zbarsky
a8948dd81e Bug 832920. Add a way for chrome iframes to opt into having a separate refresh driver (e.g. if they plan to be moved between windows) and make devtools use that opt-in. r=tnikkel,paul 2013-02-22 09:56:28 -05:00
Ryan VanderMeulen
238b010bd5 Backed out 7 changesets (bug 832920, bug 776536, bug 843261) for mochitest-a11y assertions on a CLOSED TREE.
--HG--
rename : content/base/src/NodeIterator.cpp => content/base/src/nsNodeIterator.cpp
rename : content/base/src/NodeIterator.h => content/base/src/nsNodeIterator.h
rename : content/base/src/TreeWalker.cpp => content/base/src/nsTreeWalker.cpp
rename : content/base/src/TreeWalker.h => content/base/src/nsTreeWalker.h
2013-02-28 14:41:30 -05:00
Olli Pettay
510b79b08c Bug 845631 - Remove nsXMLHttpProgressEvent, r=sicking
--HG--
extra : rebase_source : e5c6e80fbb656782bfe0f530c778cda9d9f97f0f
2013-02-28 20:53:04 +02:00
Boris Zbarsky
24d39ed923 Bug 776536 part 4. Turn on WebIDL bindings for NodeIterator and TreeWalker. r=peterv
The behavior here is a bit weird because Document is still not a
WebIDL object, so calling createNodeIterator or createTreeWalker via
an Xray will call the XPCOM versions of those methods.  That means
that I can't just disable XPCOM-based wrapping for TreeWalker and
NodeIterator altogether, unfortunately, which means a web page could
try stashing a TreeWalker in something like userdata and then getting
it back and end up wrapping it as an XPCOM object the second time.

I could "fix" that by adding a wrapper cache and whatnot, I guess, if
desired...  But the problem will go away once we convert Document in
any case.
2013-02-28 12:56:42 -05:00
Boris Zbarsky
36e1af6705 Bug 776536 part 3. Add a WebIDL API to NodeIterator and TreeWalker. r=peterv 2013-02-28 12:56:42 -05:00
Boris Zbarsky
b1917cb949 Bug 776536 part 2. Rename nsTreeWalker to mozilla::dom::TreeWalker. r=peterv
--HG--
rename : content/base/src/nsTreeWalker.cpp => content/base/src/TreeWalker.cpp
rename : content/base/src/nsTreeWalker.h => content/base/src/TreeWalker.h
2013-02-28 12:56:41 -05:00
Boris Zbarsky
8fb2a41fef Bug 776536 part 1. Rename nsNodeIterator to mozilla::dom::NodeIterator. r=peterv
--HG--
rename : content/base/src/nsNodeIterator.cpp => content/base/src/NodeIterator.cpp
rename : content/base/src/nsNodeIterator.h => content/base/src/NodeIterator.h
2013-02-28 12:56:41 -05:00
Boris Zbarsky
8d2b9f5ae9 Bug 832920. Add a way for chrome iframes to opt into having a separate refresh driver (e.g. if they plan to be moved between windows) and make devtools use that opt-in. r=tnikkel,paul 2013-02-22 09:56:28 -05:00
Ms2ger
c6832bb745 Merge m-i to b-s. 2013-02-28 14:46:10 +01:00
Ed Morley
1b556e75bc Bug 404077 - Adjust annotations of expected assertions; r=me on a CLOSED TREE 2013-02-28 13:24:36 +00:00
Gregory Szorc
27c42e83c6 Merge mozilla-central into build-system
The 3 merged files had no conflicts and were manually verified to ensure
no incompatible changes crept in.
2013-02-27 21:02:02 -08:00
Gregory Szorc
803629b9c6 Merge mozilla-central into build-system
There were merges in configure.in and some Makefile.in. None had any
conflicts. I spot verified the Makefile.in changes and confirmed that
the changes did not touch any DIRS* variables.
2013-02-27 10:03:52 -08:00
Ms2ger
2801c25ab8 Merge m-c to b-s. 2013-02-26 19:09:25 +01:00
Gregory Szorc
16f0413b0c Merge mozilla-central into build-system
Only conflict was configure.in amd was due to context, not
changed lines themselves.
2013-02-25 22:09:18 -08:00
Gregory Szorc
fee2be3026 Bug 784841 - Part 18g: Convert /content; r=glandium 2013-02-25 12:47:19 -08:00
Simon Montagu
f24942c07e Test for bug 844404 2013-02-27 09:32:50 +02:00
Simon Montagu
880ff19a9f Test for bug 841205 2013-02-27 09:32:48 +02:00
Ehsan Akhgari
621cb2d14d Bug 844169 - Part 1: Rename nsHTMLIFrameElement to mozilla::dom::HTMLIFrameElement; r=bzbarsky
--HG--
rename : content/html/content/src/nsHTMLIFrameElement.cpp => content/html/content/src/HTMLIFrameElement.cpp
rename : content/html/content/src/nsHTMLIFrameElement.h => content/html/content/src/HTMLIFrameElement.h
extra : rebase_source : 67c393954a0c46f80b8729277504e9ced5c64d33
2013-02-22 19:59:26 -05:00
Timothy Nikkel
1528be2bd9 Bug 689623. Part 12. Assume images in popups are visible. r=mats 2013-02-24 18:59:23 -06:00
Timothy Nikkel
c6b1e4c2dc Bug 689623. Part 9. Make images default to visible when they have a frame created for them. r=mats 2013-02-24 18:59:23 -06:00
Timothy Nikkel
9eabef3617 Bug 689623. Part 8. Add an 'unlocked draw' notification for images that are drawn when not locked so we catch any images that become visible through a means other than scrolling. r=joe,mats 2013-02-24 18:59:22 -06:00
Timothy Nikkel
9141b5c507 Bug 689623. Part 4. Add a visible count to nsIImadeLoadingContent, and use it when locking the image. r=joe 2013-02-24 18:59:21 -06:00
Timothy Nikkel
32f180e11f Bug 689623. Part 3. In nsImageLoadingContent add a flag to TrackImage that skips the check if we have a frame so that we can use TrackImage everywhere (including FrameCreated) instead of AddImage. r=joe 2013-02-24 18:59:21 -06:00
Timothy Nikkel
9fec1adf6b Bug 689623. Part 2. In nsImageLoadingContent make the discard request an optional part of UntrackImage so that we can use UntrackImage everywhere instead of RemoveImage. r=joe 2013-02-24 18:59:21 -06:00
Ehsan Akhgari
c3a8b72e50 Bug 844169 - Part 3: Make sure that all callers of HTMLIFrameElement.mozbrowser have chrome privileges; r=bzbarsky 2013-02-26 21:26:10 -05:00
Chris Pearce
2a8daae8a9 Bug 843849 - Make DOM/HTML fullscreen API work in Metrofox. r=bz,jimm 2013-02-28 12:28:27 +13:00
Bobby Holley
076b7bfcfa Bug 843711 - Fix up new |Components| culprits in test suite. r=mccr8 2013-02-25 10:43:03 -08:00
Jonathan Kew
3c10c07d3e bug 844454 - don't try to get a Unicode decoder for an empty charset name. r=hsivonen 2013-02-25 15:56:19 +00:00
Henri Sivonen
0b10e7dbee Bug 844792 - Warn about the upcoming removal of multipart support in XHR. r=smaug. 2013-02-25 17:12:13 +02:00
Peter Van der Beken
60efffbed9 Fix for bug 844225 (Remove some DOMCI and quickstubs). r=bz. 2013-01-10 10:54:46 +01:00
Boris Zbarsky
ec134a3b8c Bug 838686 part 2. Use NodeFilterHolder in treewalker and nodeiterator and start using WebIDL codegen for NodeFilter. r=peterv 2013-02-26 15:10:15 -05:00
L. David Baron
05d5d9dfa9 Bug 404077: Use navigator.platform.startsWith rather than navigator.platform.indexOf, at Jesse's suggestion. 2013-02-26 22:23:08 -08:00
L. David Baron
910a7adc7d Bug 404077: Do GC in a small number of tests to reduce the spread of GC-related assertions. r=Jesse 2013-02-26 22:23:08 -08:00
Ryan VanderMeulen
d06c44955f Bug 841505 et al - Disable test_xhr_timeout.html for frequent failures. r=khuey 2013-02-26 16:30:09 -05:00
Boris Zbarsky
3156f16358 Back out changeset 1c851a5bbc9f (bug 838686) because it depends on a changeset gcc doesn't like 2013-02-26 15:34:25 -05:00
Boris Zbarsky
8551942b65 Bug 838686 part 2. Use NodeFilterHolder in treewalker and nodeiterator and start using WebIDL codegen for NodeFilter. r=peterv 2013-02-26 15:10:15 -05:00
Bobby Holley
2589449122 Bug 834732 - Audit callers of GetNativeContext and use AutoPushJSContext where appropriate. r=mrbkap 2013-02-26 11:04:13 -08:00
Bobby Holley
210cff1d9f Bug 834732 - Introduce AutoPushJSContext. r=mrbkap
It's annoying to add yet another RAII class, but we're solving a different
problem here. In particular, there are lots of callers that grab a cx off
of an nsIScriptContext and use it without pushing. Most of the time this
is ok, since that cx is also the active cx. But it's hard to tell when we
might potentially violate that invariant. What's more, we don't want to just
use an nsCxPusher, because that does expensive things even when the cx matches
the one on the top of the stack. Most of these consumers should just switch
to AutoJSContext, but doing such a change en masse is a pretty risky thing to
do. So let's introduce a class that gives us good performance in the common case
and correctness in the uncommon case.
2013-02-26 11:04:12 -08:00