fixing code that relied on implicit string construction; note that |NS_LITERAL_STRING| does not produce an |nsString|, it produces something that is a |nsAReadableString|. Many functions still take |nsString&| arguments, and so |NS_LITERAL_STRING| is not appropriate in calling them, yet.

git-svn-id: svn://10.0.0.236/trunk@76734 18797224-902f-48f8-a5cc-f745e15eee43
This commit is contained in:
scc%mozilla.org
2000-08-20 00:34:08 +00:00
parent 8c476c9461
commit 9e28a8b643
12 changed files with 176 additions and 156 deletions

View File

@@ -1439,7 +1439,7 @@ nsEditor::SetDocumentCharacterSet(const PRUnichar* characterSet)
nsresult rv;
nsCOMPtr<nsIDocument> doc;
nsCOMPtr<nsIPresShell> presShell;
nsAutoString character_set = characterSet;
nsAutoString character_set(characterSet);
if (characterSet==nsnull) return NS_ERROR_NULL_POINTER;
@@ -3866,7 +3866,7 @@ nsEditor::NodeIsType(nsIDOMNode *aNode, nsIAtom *aTag)
element->GetTagName(tag);
const PRUnichar *unicodeString;
aTag->GetUnicode(&unicodeString);
if (tag.EqualsIgnoreCase(unicodeString))
if (tag.EqualsIgnoreCase(nsAutoString(unicodeString)))
{
return PR_TRUE;
}