LoadObject, respectively, in order to make it clear what they do rather than
prescribing when they should be called. r+sr=bz
git-svn-id: svn://10.0.0.236/trunk@186776 18797224-902f-48f8-a5cc-f745e15eee43
- Make object frames have no children
- Make the frame constructor construct a subdocumentframe, object frame or
image frame as appropriate
- start the load of <applet>, <embed> and <object> in content code
- fallback to alternate rendering correctly
NOTE: This checkin will break the plugin finder. This will be fixed soon.
r+sr=bz
git-svn-id: svn://10.0.0.236/trunk@180762 18797224-902f-48f8-a5cc-f745e15eee43
285428, r=biesi, sr=jst (note: sr was given in bug 286000 as part of the patch
there).
git-svn-id: svn://10.0.0.236/trunk@171771 18797224-902f-48f8-a5cc-f745e15eee43
o) move nsCopySupport into content (from layout), it belongs there better
o) add an |currentURI| attribute to nsIImageLoadingContent which allows access to the URI that is currently being displayed
o) use that from the image uri copy code
xpfe part: r=neil.parkwaycc.co.uk sr=bz rest: r+sr=bz
git-svn-id: svn://10.0.0.236/trunk@157435 18797224-902f-48f8-a5cc-f745e15eee43
bug 191839. Original patch and hard work by Tim <riceman+bmo@mail.rit.edu>, r=bzbarsky (on backend stuff), r=neil (on the tabbrowser stuff), sr=bzbarsky
git-svn-id: svn://10.0.0.236/trunk@156366 18797224-902f-48f8-a5cc-f745e15eee43
start loading the background images when we resolve style on an object that
needs them instead of when we scroll down and see it for the first time. Bug
57607, r=pavlov, sr=dbaron
git-svn-id: svn://10.0.0.236/trunk@153725 18797224-902f-48f8-a5cc-f745e15eee43
for a frame if we've had a frame at some point in the past; this should keep us
from calling GetPrimaryFrameFor quite so much during pageload. Bug 225848,
r+sr=jst
git-svn-id: svn://10.0.0.236/trunk@149399 18797224-902f-48f8-a5cc-f745e15eee43
