whole_func_string: function getTextRangeBoundaryPosition(textRange, wholeRangeContainerElement, isStart, isCollapsed) {
          var workingRange = textRange.duplicate();
  
          workingRange.collapse(isStart);
          var containerElement = workingRange.parentElement();
  
          // Sometimes collapsing a TextRange that's at the start of a text node can move it into the previous node, so
          // check for that
          // TODO: Find out when. Workaround for wholeRangeContainerElement may break this
          if (!dom.isAncestorOf(wholeRangeContainerElement, containerElement, true)) {
              containerElement = wholeRangeContainerElement;
  
          }
  
  
  
          // Deal with nodes that cannot "contain rich HTML markup". In practice, this means form inputs, images and
          // similar. See http://msdn.microsoft.com/en-us/library/aa703950%28VS.85%29.aspx
          if (!containerElement.canHaveHTML) {
              return new DomPosition(containerElement.parentNode, dom.getNodeIndex(containerElement));
          }
  
          var workingNode = dom.getDocument(containerElement).createElement("span");
          var comparison, workingComparisonType = isStart ? "StartToStart" : "StartToEnd";
          var previousNode, nextNode, boundaryPosition, boundaryNode;
  
          // Move the working range through the container's children, starting at the end and working backwards, until the
          // working range reaches or goes past the boundary we're interested in
          do {
              containerElement.insertBefore(workingNode, workingNode.previousSibling);
              workingRange.moveToElementText(workingNode);
          } while ( (comparison = workingRange.compareEndPoints(workingComparisonType, textRange)) > 0 &&
                  workingNode.previousSibling);
  
          // We've now reached or gone past the boundary of the text range we're interested in
          // so have identified the node we want
          boundaryNode = workingNode.nextSibling;
  
          if (comparison == -1 && boundaryNode && dom.isCharacterDataNode(boundaryNode)) {
              // This is a character data node (text, comment, cdata). The working range is collapsed at the start of the
              // node containing the text range's boundary, so we move the end of the working range to the boundary point
              // and measure the length of its text to get the boundary's offset within the node.
              workingRange.setEndPoint(isStart ? "EndToStart" : "EndToEnd", textRange);
  
  
              var offset;
  
              if (/[\r\n]/.test(boundaryNode.data)) {
                  /*
                  For the particular case of a boundary within a text node containing line breaks (within a <pre> element,
                  for example), we need a slightly complicated approach to get the boundary's offset in IE. The facts:
  
                  - Each line break is represented as \r in the text node's data/nodeValue properties
                  - Each line break is represented as \r\n in the TextRange's 'text' property
                  - The 'text' property of the TextRange does not contain trailing line breaks
  
                  To get round the problem presented by the final fact above, we can use the fact that TextRange's
                  moveStart() and moveEnd() methods return the actual number of characters moved, which is not necessarily
                  the same as the number of characters it was instructed to move. The simplest approach is to use this to
                  store the characters moved when moving both the start and end of the range to the start of the document
                  body and subtracting the start offset from the end offset (the "move-negative-gazillion" method).
                  However, this is extremely slow when the document is large and the range is near the end of it. Clearly
                  doing the mirror image (i.e. moving the range boundaries to the end of the document) has the same
                  problem.
  
                  Another approach that works is to use moveStart() to move the start boundary of the range up to the end
                  boundary one character at a time and incrementing a counter with the value returned by the moveStart()
                  call. However, the check for whether the start boundary has reached the end boundary is expensive, so
                  this method is slow (although unlike "move-negative-gazillion" is largely unaffected by the location of
                  the range within the document).
  
                  The method below is a hybrid of the two methods above. It uses the fact that a string containing the
                  TextRange's 'text' property with each \r\n converted to a single \r character cannot be longer than the
                  text of the TextRange, so the start of the range is moved that length initially and then a character at
                  a time to make up for any trailing line breaks not contained in the 'text' property. This has good
                  performance in most situations compared to the previous two methods.
                  */
                  var tempRange = workingRange.duplicate();
                  var rangeLength = tempRange.text.replace(/\r\n/g, "\r").length;
  
                  offset = tempRange.moveStart("character", rangeLength);
                  while ( (comparison = tempRange.compareEndPoints("StartToEnd", tempRange)) == -1) {
                      offset++;
                      tempRange.moveStart("character", 1);
                  }
              } else {
                  offset = workingRange.text.length;
              }
              boundaryPosition = new DomPosition(boundaryNode, offset);
          } else {
  
  
              // If the boundary immediately follows a character data node and this is the end boundary, we should favour
              // a position within that, and likewise for a start boundary preceding a character data node
              previousNode = (isCollapsed || !isStart) && workingNode.previousSibling;
              nextNode = (isCollapsed || isStart) && workingNode.nextSibling;
  
  
  
              if (nextNode && dom.isCharacterDataNode(nextNode)) {
                  boundaryPosition = new DomPosition(nextNode, 0);
              } else if (previousNode && dom.isCharacterDataNode(previousNode)) {
                  boundaryPosition = new DomPosition(previousNode, previousNode.length);
              } else {
                  boundaryPosition = new DomPosition(containerElement, dom.getNodeIndex(workingNode));
              }
          }
  
          // Clean up
          workingNode.parentNode.removeChild(workingNode);
  
          return boundaryPosition;
      }
func_code_string: function getTextRangeBoundaryPosition(textRange, wholeRangeContainerElement, isStart, isCollapsed) {
          var workingRange = textRange.duplicate();
  
          workingRange.collapse(isStart);
          var containerElement = workingRange.parentElement();
  
          // Sometimes collapsing a TextRange that's at the start of a text node can move it into the previous node, so
          // check for that
          // TODO: Find out when. Workaround for wholeRangeContainerElement may break this
          if (!dom.isAncestorOf(wholeRangeContainerElement, containerElement, true)) {
              containerElement = wholeRangeContainerElement;
  
          }
  
  
  
          // Deal with nodes that cannot "contain rich HTML markup". In practice, this means form inputs, images and
          // similar. See http://msdn.microsoft.com/en-us/library/aa703950%28VS.85%29.aspx
          if (!containerElement.canHaveHTML) {
              return new DomPosition(containerElement.parentNode, dom.getNodeIndex(containerElement));
          }
  
          var workingNode = dom.getDocument(containerElement).createElement("span");
          var comparison, workingComparisonType = isStart ? "StartToStart" : "StartToEnd";
          var previousNode, nextNode, boundaryPosition, boundaryNode;
  
          // Move the working range through the container's children, starting at the end and working backwards, until the
          // working range reaches or goes past the boundary we're interested in
          do {
              containerElement.insertBefore(workingNode, workingNode.previousSibling);
              workingRange.moveToElementText(workingNode);
          } while ( (comparison = workingRange.compareEndPoints(workingComparisonType, textRange)) > 0 &&
                  workingNode.previousSibling);
  
          // We've now reached or gone past the boundary of the text range we're interested in
          // so have identified the node we want
          boundaryNode = workingNode.nextSibling;
  
          if (comparison == -1 && boundaryNode && dom.isCharacterDataNode(boundaryNode)) {
              // This is a character data node (text, comment, cdata). The working range is collapsed at the start of the
              // node containing the text range's boundary, so we move the end of the working range to the boundary point
              // and measure the length of its text to get the boundary's offset within the node.
              workingRange.setEndPoint(isStart ? "EndToStart" : "EndToEnd", textRange);
  
  
              var offset;
  
              if (/[\r\n]/.test(boundaryNode.data)) {
                  /*
                  For the particular case of a boundary within a text node containing line breaks (within a <pre> element,
                  for example), we need a slightly complicated approach to get the boundary's offset in IE. The facts:
  
                  - Each line break is represented as \r in the text node's data/nodeValue properties
                  - Each line break is represented as \r\n in the TextRange's 'text' property
                  - The 'text' property of the TextRange does not contain trailing line breaks
  
                  To get round the problem presented by the final fact above, we can use the fact that TextRange's
                  moveStart() and moveEnd() methods return the actual number of characters moved, which is not necessarily
                  the same as the number of characters it was instructed to move. The simplest approach is to use this to
                  store the characters moved when moving both the start and end of the range to the start of the document
                  body and subtracting the start offset from the end offset (the "move-negative-gazillion" method).
                  However, this is extremely slow when the document is large and the range is near the end of it. Clearly
                  doing the mirror image (i.e. moving the range boundaries to the end of the document) has the same
                  problem.
  
                  Another approach that works is to use moveStart() to move the start boundary of the range up to the end
                  boundary one character at a time and incrementing a counter with the value returned by the moveStart()
                  call. However, the check for whether the start boundary has reached the end boundary is expensive, so
                  this method is slow (although unlike "move-negative-gazillion" is largely unaffected by the location of
                  the range within the document).
  
                  The method below is a hybrid of the two methods above. It uses the fact that a string containing the
                  TextRange's 'text' property with each \r\n converted to a single \r character cannot be longer than the
                  text of the TextRange, so the start of the range is moved that length initially and then a character at
                  a time to make up for any trailing line breaks not contained in the 'text' property. This has good
                  performance in most situations compared to the previous two methods.
                  */
                  var tempRange = workingRange.duplicate();
                  var rangeLength = tempRange.text.replace(/\r\n/g, "\r").length;
  
                  offset = tempRange.moveStart("character", rangeLength);
                  while ( (comparison = tempRange.compareEndPoints("StartToEnd", tempRange)) == -1) {
                      offset++;
                      tempRange.moveStart("character", 1);
                  }
              } else {
                  offset = workingRange.text.length;
              }
              boundaryPosition = new DomPosition(boundaryNode, offset);
          } else {
  
  
              // If the boundary immediately follows a character data node and this is the end boundary, we should favour
              // a position within that, and likewise for a start boundary preceding a character data node
              previousNode = (isCollapsed || !isStart) && workingNode.previousSibling;
              nextNode = (isCollapsed || isStart) && workingNode.nextSibling;
  
  
  
              if (nextNode && dom.isCharacterDataNode(nextNode)) {
                  boundaryPosition = new DomPosition(nextNode, 0);
              } else if (previousNode && dom.isCharacterDataNode(previousNode)) {
                  boundaryPosition = new DomPosition(previousNode, previousNode.length);
              } else {
                  boundaryPosition = new DomPosition(containerElement, dom.getNodeIndex(workingNode));
              }
          }
  
          // Clean up
          workingNode.parentNode.removeChild(workingNode);
  
          return boundaryPosition;
      }
func_documentation_string: Gets the boundary of a TextRange expressed as a node and an offset within that node. This function started out as an improved version of code found in Tim Cameron Ryan's IERange (http://code.google.com/p/ierange/) but has grown, fixing problems with line breaks in preformatted text, adding workaround for IE TextRange bugs, handling for inputs and images, plus optimizations.