9538 2010-04-16 09:23:51 +0000 Improve code references 2010-04-26 11:54:14 +0000 1 1 1 Unclassified mobileOK Basic checker Java Library unspecified PC Linux RESOLVED FIXED P2 enhancement --- 1 fd fd oldest_to_newest 35098 0 fd 2010-04-16 09:23:51 +0000 For users, reports of errors are way more useful when they have some direct way to see where the error occurred. Depending on the test, and in particular on how the test is actually conducted (XSLT, Java, third-party library), the mobileOK Checker returns incriminated code in inconsistent ways, sometimes with line and column information, sometimes without, sometimes with wrong info (see Bug 7208). Try to improve the situation and report line info as much as possible. 35257 1 fd 2010-04-26 11:54:14 +0000 More specific code extracts are now returned. Depending on the test, this means: - either the incriminated tag and the tag only, which is typically useful for errors triggered by specific attribute values. - or the incriminated tag along with the beginning (about 40 characters) of its content. See also Bug 6962