Databases
StackOverflow2013
Postsdbo
POFreezing the DOM to JavaScript: Overwriting DOM modification functions as no-ops
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POFreezing the DOM to JavaScript: Overwriting DOM modification functions as no-ops
    primarykey
    data
    text
    <p>I'm writing a piece of code that requires the <code>DOM</code> of a website to remain frozen while arbitrary JavaScript runs. Attributes changing is fine but I can't have anything changing the original tag structure of the page!</p> <p>I know in JavaScript there are a base number of functions that can modify the <code>DOM</code>:</p> <pre><code>appendChild( nodeToAppend ) cloneNode( true|false ) createElement( tagName ) createElemeentNS( namespace, tagName ) createTextNode( textString ) innerHTML insertBefore( nodeToInsert, nodeToInsertBefore ) removeChild( nodetoRemove ) replacechild( nodeToInsert, nodeToReplace ) </code></pre> <p>My initial thought was simply to overwrite these functions as no ops:</p> <pre><code>&gt;&gt;&gt; document.write('&lt;p&gt;Changing your DOM. Mwwhaha!&lt;/p&gt;') &gt;&gt;&gt; document.write = function() {} &gt;&gt;&gt; document.write('&lt;p&gt;No-op now!&lt;/p&gt;') </code></pre> <p>While it's easy to do this for the <code>document</code> object the <code>DOM</code> modification functions can be called from many different JavaScript objects! If I could overwrite these functions at top level perhaps it would work?</p> <p>Update from sktrdie:</p> <pre><code>&gt;&gt;&gt; HTMLElement.prototype.appendChild = function(){} &gt;&gt;&gt; $("a").get(0).appendChild(document.createElement("div")) # Still works argh. &gt;&gt;&gt; HTMLAnchorElement.prototype.appendChild = function(){} &gt;&gt;&gt; $("a").get(0).appendChild(document.createElement("div")) # No-op yeah! </code></pre> <p>So it would seem I could just gather the constructors of all <code>DOM</code> elements and run over them putting in no-ops but that still seems pretty messy ... </p> <p><strong>How can I protect the <code>DOM</code> from modification from arbitrary JavaScript?</strong></p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USjb.
    1. USjb.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POFreezing the DOM to JavaScript: Overwriting DOM modification functions as no-ops
      1. This table or related slice is empty.
      1. VTUpMod
    1. COWow. What are you doing this for? Really curious.
      singulars
      1. POFreezing the DOM to JavaScript: Overwriting DOM modification functions as no-ops
      1. USCrescent Fresh
    2. COI've got an iFrame that proxies in a webpage showing the site. You then pick bits of the site using JavaScript I inject - I'm grabbing CSS selectors off what you pick. So the `DOM` needs to stay the same or the selectors will break (but other JavaScript should run as normal!)
      singulars
      1. POFreezing the DOM to JavaScript: Overwriting DOM modification functions as no-ops
      1. USjb.
    3. COSo specifically you want to stop the javascript that is loaded in the *child* iframe from modifying the DOM?
      singulars
      1. POFreezing the DOM to JavaScript: Overwriting DOM modification functions as no-ops
      1. USCrescent Fresh
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload