User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5; MultiZilla v220.127.116.11g) Gecko/20031007 MultiZilla/18.104.22.168l Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5; MultiZilla v22.214.171.124g) Gecko/20031007 MultiZilla/126.96.36.199l I a web page contains the null character (ascii 0), view selection source sees this character as the end of string sentinel. Therefore the popup menu item "View Selection Source" doesn't appear if this character is the first selected character. Using � is equally good (bad). I understand that this is an inherent problem with C strings. I would appear that other functions relating to the current selection may also be affected, for instance the Web Search for "..." function also truncates the string. In addition to the context menu, the actual source window displayed cuts the character out, along with some of the surrounding text. I get "null characcode>'" when it should be "null character <code>'?'</code>". (The full view source window is correct - it displays a box character where the question mark is). Reproducible: Always Steps to Reproduce: 1. Create a web page with a null character (ascii 0) in the text. 2. Select text starting with the null character (it should be displayed as a box character). Select any amount of text as long as the null character is the first. 3. Right click to open the context menu and observe that no context menu items relating to selected text appear. 4. Select some text including the null character as any character (aside from the first). 5. Right click to open the context menu and observe that the 'Web search for "..."' menu item truncates the text at the null character. Actual Results: The null character appears to be acting as the end of string sentinel and causing the context menu to display the wrong information. Expected Results: The null character should could as a character in this aspect.
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.