Prettify expanded inspection tooltips inside editor

2026-09-27 10:03:11 +07:00 · 2012-07-11 15:54:12 +02:00
parent ade996a85b
commit 7eeeec4ba5
652 changed files with 693 additions and 32 deletions
@@ -2,6 +2,7 @@
 <body>
 This inspection reports usages of absolute alignment constants from AWT and Swing. Internationalized applications should make use of
 relative alignment, because it respects locale component orientation settings.
+<!-- tooltip end -->
 <p>
 <small>New in 11, Powered by InspectionGadgets</small>
 </body>
@@ -1,6 +1,7 @@
 <html>
 <body>
 This inspection reports abstract classes which extend concrete classes.
+<!-- tooltip end -->
 <p>
 <small>Powered by InspectionGadgets</small>
 </body>
@@ -2,6 +2,7 @@
 <body>
 This inspection reports abstract classes which have no
 concrete subclasses.
+<!-- tooltip end -->
 <p>
 <small>Powered by InspectionGadgets</small>
 </body>
@@ -7,6 +7,7 @@ This inspection reports abstract classes which have precisely one
 direct inheritor. While such classes may offer admirable clarity of design,
 in memory-constrained or bandwidth-limited environments, they needlessly increase
 the total footprint of the application. Consider merging the abstract class with its inheritor.
+<!-- tooltip end -->
 <p>
 <small>Powered by InspectionGadgets</small>
 </body>
@@ -1,6 +1,7 @@
 <html>
 <body>
 This inspection reports abstract classes without abstract methods.
+<!-- tooltip end -->
 <p>
 <small>Powered by InspectionGadgets</small>
 </body>
@@ -3,6 +3,7 @@
 This inspection reports any calls of abstract methods within a constructor of an
 abstract class. Such calls may result in subtle bugs, as the object is not guaranteed to be initialized
 before the method call occurs.
+<!-- tooltip end -->
 <p>
 <small>Powered by InspectionGadgets</small>
 </body>
@@ -3,6 +3,7 @@
 This inspection reports <b>abstract</b> methods which override <b>abstract</b> methods. Methods with
 different return types or exception declarations than the method they override are not
 reported by this inspection.
+<!-- tooltip end -->
 <p>
 Use the first checkbox to ignore any abstract methods that have a different JavaDoc comment than their super method.
 <p>
@@ -3,6 +3,7 @@
 This inspection reports abstract methods which override concrete methods.
 Methods overridden from <b>java.lang.Object</b> are not reported
 by this inspection.
+<!-- tooltip end -->
 <p>
 <small>Powered by InspectionGadgets</small>
 </body>
@@ -3,6 +3,7 @@
 This inspection reports any abstract methods which are not implemented in every concrete
 subclass. This is a compile-time error on the subclasses, while this inspection
 reports the problem at the point of the abstract method.
+<!-- tooltip end -->
 <p>
 <small>Powered by InspectionGadgets</small>
 </body>
@@ -4,6 +4,7 @@ This inspection reports on any access to a <b>static</b> field
 of any non-threadsafe type specified below, which is accessed from an instance field or a
 non-synchronized block. It is possible that the static field is accessed from
 multiple threads, which can lead to unspecified side effects.
+<!-- tooltip end -->
 <p>
 <small>Powered by InspectionGadgets</small>
 </body>
@@ -4,6 +4,7 @@ This inspection reports on any access to a non-constant <b>static</b> field whic
 locked on either <b>this</b> or an instance field of <b>this</b>.
 Locking a <b>static</b> field on instance data does not prevent the field from being
 modified by other instances, and thus may result in surprising race conditions.
+<!-- tooltip end -->
 <p>
 <small>Powered by InspectionGadgets</small>
 </body>
@@ -17,6 +17,7 @@ accessed, when in fact a field from the super class is accessed. To make the int
  }
 }
 </code></pre>
+<!-- tooltip end -->
 <p>
 <small>New in 11, Powered by InspectionGadgets</small>
 </body>
@@ -6,6 +6,7 @@ reader of the code may think that a method in the surrounding class is
 called, when in fact a method from the super class is called. To make the
 intent of the code more clear it is recommended to add a
 <b>super</b> qualifier to the method call.
+<!-- tooltip end -->
 <p>
 <small>New in 8, Powered by InspectionGadgets</small>
 </body>
@@ -2,6 +2,7 @@
 <body>
 This inspection reports any uses of annotations.
 Annotations are not supported under Java 1.4 or earlier JVMs.
+<!-- tooltip end -->
 <p>
 <small>Powered by InspectionGadgets</small>
 </body>
@@ -2,6 +2,7 @@
 <body>
 This inspection reports annotation interfaces.
 Such interfaces are not supported under Java 1.4 or earlier JVMs.
+<!-- tooltip end -->
 <p>
 <small>Powered by InspectionGadgets</small>
 </body>
@@ -2,6 +2,7 @@
 <body>
 This inspection reports annotation classes whose names are either too short, too long, or do not follow
 the specified regular expression pattern.
+<!-- tooltip end -->
 <p>
 Use the fields provided below to specify minimum length, maximum length and regular expression expected for annotation names.
 (Regular expressions are in standard <b>java.util.regex</b> format.)
@@ -5,6 +5,7 @@ total complexity of a class is the sum of the cyclomatic complexities of all the
 and initializers the class declares. Inherited methods and initializers are not counted
 toward the total complexity. Anonymous classes with more than very low complexities may be
 difficult to understand, and should probably be promoted to become named inner classes.
+<!-- tooltip end -->
 <p>
 Use the field provided below to specify the maximum acceptable complexity a class might have.
 <p>
@@ -3,6 +3,7 @@
 This inspection reports anonymous inner class with too many methods.
 Anonymous classes with more than a very low number of methods may be
 difficult to understand, and should probably be promoted to become named inner classes.
+<!-- tooltip end -->
 <p>
 Use the field provided below to specify the maximum acceptable number of methods
 an anonymous inner class might have.
@@ -2,6 +2,7 @@
 <body>
 This inspection reports anonymous class variables being named identically to variables of a containing method.
 Such a variable name may be confusing.
+<!-- tooltip end -->
 <p>
 <small>Powered by InspectionGadgets</small>
 </body>
@@ -2,6 +2,7 @@
 <body>
 This inspection reports any anonymous inner classes.
 Some code standards discourage the use of anonymous inner classes.
+<!-- tooltip end -->
 <p>
 <small>Powered by InspectionGadgets</small>
 </body>
@@ -6,6 +6,7 @@ Applying the results of this inspection without consideration might have negativ
 This inspection reports any anonymous inner classes which may safely be made into a named
 <b>static</b> inner class. An inner class may be static if it doesn't reference
 its enclosing class instance or local variables. A static inner class uses slightly less memory.
+  <!-- tooltip end -->
 <p>
 <small>Powered by InspectionGadgets</small>
 </body>
@@ -5,6 +5,7 @@ These methods fetch integer and boolean values from the
 system properties for a given key. Due to their underexpressive names and confusing
 location of functionality, it's easy for novice programmers to attempt to use these
 for other purposes, such as string parsing.
+<!-- tooltip end -->
 <p>
 <small>Powered by InspectionGadgets</small>
 </body>
@@ -2,6 +2,7 @@
 <body>
 This inspection reports any use of <b>==</b> to test for Array equality,
 rather than the <b>"java.util.Arrays.equals()"</b> method.
+<!-- tooltip end -->
 <p>
 <small>New in 10.5, Powered by InspectionGadgets</small>
 </body>
@@ -6,6 +6,7 @@ compares identity and is equivalent to using <b>==</b>. Use
 <b>Arrays.equals()</b> to compare the contents of two arrays
 or <b>Arrays.deepEquals()</b> to compare the content of two
 multi-dimensional arrays.
+<!-- tooltip end -->
 <p>
 <small>Powered by InspectionGadgets</small>
 </body>
@@ -5,6 +5,7 @@ on an array. To get the same hash code for two arrays
 with identical contents call <b>Arrays.hashCode()</b>.
 Use <b>Arrays.deepHashCode()</b> to calculate the hash
 code of a multi-dimensional array.
+<!-- tooltip end -->
 <p>
 <small>New in 10.5, Powered by InspectionGadgets</small>
 </body>
@@ -6,6 +6,7 @@ Applying the results of this inspection without consideration might have negativ
 This inspection reports any access to the <b>.length</b> of an array in the condition part of a
 loop statement. In highly resource constrained environments, such calls may
 have adverse performance implications.
+  <!-- tooltip end -->
 <p>
 <small>Powered by InspectionGadgets</small>
 </body>
@@ -3,6 +3,7 @@
 This inspection reports variables, methods, or classes named
 <b>assert</b>. Such names are legal under Java 1.3 or
 earlier JVMs, but will cause problems under Java 1.4 or later.
+<!-- tooltip end -->
 <p>
 <small>Powered by InspectionGadgets</small>
 </body>
@@ -3,6 +3,7 @@
 This inspection reports any calls to JUnit's <b>assertEquals()</b>
 method where the expected result and actual result arguments are of incompatible
 types. While such a call might theoretically be useful, most likely it represents a bug.
+<!-- tooltip end -->
 <p>
 <small>Powered by InspectionGadgets</small>
 </body>
@@ -3,6 +3,7 @@
 This inspection reports any calls to JUnit's <b>assertEquals()</b>
 method with arguments of type array. Arrays should be checked with one of the
 <b>assertArrayEquals()</b> methods.
+<!-- tooltip end -->
 <p>
 <small>New in 10, Powered by InspectionGadgets</small>
 </body>
@@ -5,6 +5,7 @@ or <b>junit.framework.Assert.assertEquals()</b> which
 can be replaced with an equivalent call to <b>assertSame()</b>.
 This is possible when the arguments are instances of a final class which does not override
 the <b>equals()</b> method.
+<!-- tooltip end -->
 <p>
 <small>Powered by InspectionGadgets</small>
 </body>
@@ -2,6 +2,7 @@
 <body>
 This inspection reports <b>assert</b> statements.
 Such statements are not supported under Java 1.3 or earlier JVMs.
+<!-- tooltip end -->
 <p>
 <small>Powered by InspectionGadgets</small>
 </body>
@@ -6,6 +6,7 @@ switched off, the side effects are not guaranteed to happen and can cause subtle
 Common unwanted side effects detected by this inspection are modifications of variables
 and fields in the assert statement. Also methods called are analyzed one level deep
 for any modifications of fields.
+<!-- tooltip end -->
 <p>
 <small>Powered by InspectionGadgets</small>
 </body>
@@ -4,6 +4,7 @@ This inspection reports calls to JUnit <b>assertXXX()</b> or
 <b>fail()</b> methods that don't
 report an error message on assertion failure. Error messages may help clarify the test case's
 intent.
+<!-- tooltip end -->
 <p>
 <small>Powered by InspectionGadgets</small>
 </body>
@@ -2,6 +2,7 @@
 <body>
 This inspection reports assignment to variable declared as a <b>catch</b> block parameter.
 While occasionally intended, this construct can be confusing.
+<!-- tooltip end -->
 <p>
 <small>Powered by InspectionGadgets</small>
 </body>
@@ -4,6 +4,7 @@ This inspection reports any attempt to assign an array or <b>Collection</b> fiel
 Since the array or <b>Collection</b> may have its contents modified by the calling method, this construct may
 result in an object having its state modified unexpectedly. While occasionally useful for performance
 reasons, this construct is inherently bug-prone.
+<!-- tooltip end -->
 <p>
 <small>Powered by InspectionGadgets</small>
 </body>
@@ -6,6 +6,7 @@ Since <b>Date</b> or <b>Calendar</b> are often
 treated as immutable values but are actually mutable, assigning to such a field from a method parameter may
 result in an object having its state modified unexpectedly. While occasionally useful for performance
 reasons, this construct is inherently bug-prone.
+<!-- tooltip end -->
 <p>
 <small>Powered by InspectionGadgets</small>
 </body>
@@ -3,6 +3,7 @@
 This inspection reports assignment a variable declared in a <b>for</b> statement
 in the body of that statement. It also reports any attempt to increment or decrement the variable.
 While occasionally intended, this construct can be extremely confusing, and is often the result of a typo.
+<!-- tooltip end -->
 <p>
 <small>Powered by InspectionGadgets</small>
 </body>
@@ -3,6 +3,7 @@
 This inspection reports assignment to a
 variable declared as a method parameter. It also reports any attempt to increment or decrement the variable.
 While occasionally intended, this construct can be extremely confusing, and is often the result of a typo.
+<!-- tooltip end -->
 <p>
 <small>Powered by InspectionGadgets</small>
 </body>
@@ -6,6 +6,7 @@ While occasionally useful for triggering garbage collection, this
 construct may make the code more prone
 to NullPointerExceptions, and often indicates that the developer doesn't
 really understand the class's intended semantics.
+<!-- tooltip end -->
 <p>
 Use the checkbox below to ignore assignments to fields.
 <p>
@@ -4,6 +4,7 @@ This inspection reports any assignments to <b>static</b> fields from within
 instance methods. While legal, such assignments are tricky to do
 safely, and are often a result of fields being inadvertently marked
 <b>static</b>.
+<!-- tooltip end -->
 <p>
 <small>Powered by InspectionGadgets</small>
 </body>
@@ -5,6 +5,7 @@ used as the condition of an <b>if</b>, <b>while</b>, <b>for</b> or
 <b>do</b> statement. While occasionally intended,
 this usage is confusing, and often indicates a typo
 (<b>=</b> instead of <b>==</b>).
+<!-- tooltip end -->
 <p>
 <small>Powered by InspectionGadgets</small>
 </body>
@@ -2,6 +2,7 @@
 <body>
 This inspection reports "auto-boxing", i.e. the automatic wrapping of primitive values as objects, where needed.
 Code which relies on auto-boxing will not work in pre-Java 5.0 environments.
+<!-- tooltip end -->
 <p>
 <small>Powered by InspectionGadgets</small>
 </body>
@@ -2,6 +2,7 @@
 <body>
 This inspection reports "auto-unboxing", e.g. the automatic unwrapping of objects into primitive values, where needed.
 Code which relies on auto-boxing will not work in pre-Java 5.0 environments.
+<!-- tooltip end -->
 <p>
 <small>Powered by InspectionGadgets</small>
 </body>
@@ -4,6 +4,7 @@ This inspection reports on any call to <b>java.util.concurrent.locks.Condition.a
 <b>await()</b> and related methods are normally
 used to suspend a thread until a condition is signalled as true, and that condition should be checked after the <b>await()</b>
 returns. A loop is the clearest way to achieve this.
+<!-- tooltip end -->
 <p>
 <small>Powered by InspectionGadgets</small>
 </body>
@@ -4,6 +4,7 @@ This inspection reports on any call to <b>Condition.signal()</b>
 or <b>Condition.signalAll()</b>
 for which no call to a corresponding <b>Condition.await()</b>
 can be found. Only calls which target fields of the current class are reported by this inspection.
+<!-- tooltip end -->
 <p>
 <small>Powered by InspectionGadgets</small>
 </body>
@@ -5,6 +5,7 @@ which catch inappropriate exceptions. Some exceptions, for instance
 <b>java.lang.NullPointerException</b> and
 <b>java.lang.IllegalMonitorStateException</b> represent programming errors
 and so should almost certainly not be caught in production code.
+<!-- tooltip end -->
 <p>
 Use the list below to specify which exceptions should be flagged by this inspection.
 <p>
@@ -3,8 +3,8 @@
 This inspection reports <b>throw</b> statements
 which throw inappropriate exceptions. One use of this inspection would be to warn of
 <b>throw</b> statements which throw overly generic exceptions
-(e.g. <b>java.lang.Exception</b> or
-<b>java.io.IOException</b>).
+(e.g. <b>java.lang.Exception</b> or <b>java.io.IOException</b>).
+<!-- tooltip end -->
 <p>
 Use the list below to specify which exceptions should be flagged by this inspection.
 <p>
@@ -4,6 +4,7 @@ This inspection reports any checks for oddness of the form:
 <code><pre>x % 2 == 1</pre></code>
 Such checks will fail for negative odd values, which is probably not the behaviour intended. Consider using:
 <code><pre>x % 2 != 0</pre></code> or: <code><pre>(x & 1) == 1</pre></code> instead.
+<!-- tooltip end -->
 <p>
 <small>Powered by InspectionGadgets</small>
 </body>
@@ -4,6 +4,7 @@ This inspection reports JUnit 4.0 <b>@BeforeClass</b> or <b>@AfterClass</b> meth
 is not declared
 <b>public static</b>, does not return <b>void</b>, or takes arguments.
 Such methods are easy to create inadvertently, and will not be executed by JUnit tests runners.
+<!-- tooltip end -->
 <p>
 <small>Powered by InspectionGadgets</small>
 </body>
@@ -4,6 +4,7 @@ This inspection reports JUnit 4.0 <b>@Before</b> or <b>@After</b> method
 is not declared
 <b>public</b>, does not return <b>void</b>, or takes arguments.
 Such methods are easy to create inadvertently, and will not be executed by JUnit tests runners.
+<!-- tooltip end -->
 <p>
 <small>Powered by InspectionGadgets</small>
 </body>
@@ -6,6 +6,7 @@ a mistake, as two <b>java.math.BigDecimal</b>s are only equal if
 they are equal in both value and scale, so that 2.0 is not equal to 2.00
 To compare <b>java.math.BigDecimal</b>s for mathematical equality,
 use <b>.compareTo()</b> instead.
+<!-- tooltip end -->
 <p>
 <small>Powered by InspectionGadgets</small>
 </body>
@@ -3,6 +3,7 @@
 This inspection reports any attempt to instantiate a new <b>Boolean</b>
 object. Constructing new <b>Boolean</b> objects is rarely necessary,
 and may cause performance problems if done often enough.
+<!-- tooltip end -->
 <p>
 <small>Powered by InspectionGadgets</small>
 </body>
@@ -19,5 +19,8 @@ For example:
  <b>boolean</b> member = !inverted();
 }  
 </pre></code>
+<!-- tooltip end -->
+<p>
+<small>Powered by InspectionGadgets</small>
 </body>
 </html>
@@ -2,6 +2,7 @@
 <body>
 This inspection reports boolean methods whose names do not start with a question
 word. Boolean methods that override library methods are ignored by this inspection.
+<!-- tooltip end -->
 <p>
 Use the list below to specify acceptable question words to start boolean method names with.
 <p>
@@ -2,6 +2,7 @@
 <body>
 This inspection reports any boolean variables or fields which are always negated
 when its value is used.
+<!-- tooltip end -->
 <p>
 <small>New in 11, Powered by InspectionGadgets</small>
 </body>
@@ -4,6 +4,7 @@ This inspection reports boxing of already boxed values. This is a useless
 operation since any boxed value will first be auto-unboxed before boxing the
 value again. If done inside an inner loop such code may cause performance
 problems.
+<!-- tooltip end -->
 <p>
 <small>New in 10.0.2, Powered by InspectionGadgets</small>
 </body>
@@ -3,6 +3,7 @@
 This inspection reports <b>break</b> statements,
 other than at the end of a <b>switch</b> statement branch.
 <b>break</b> statements complicate refactoring, and can be confusing.
+<!-- tooltip end -->
 <p>
 <small>Powered by InspectionGadgets</small>
 </body>
@@ -2,6 +2,7 @@
 <body>
 This inspection reports <b>break</b> statements with labels.
 Labeled <b>break</b> statements complicate refactoring, and can be confusing.
+<!-- tooltip end -->
 <p>
 <small>Powered by InspectionGadgets</small>
 </body>
@@ -3,6 +3,7 @@
 This inspection reports calls to <b>java.lang.Thread.sleep()</b> that occur inside loops. Such calls
 are indicative of "busy-waiting". Busy-waiting is often inefficient, and may result in unexpected deadlocks
 as busy-waiting threads do not release locked resources.
+<!-- tooltip end -->
 <p>
 <small>Powered by InspectionGadgets</small>
 </body>
@@ -2,6 +2,7 @@
 <body>
 This inspection reports array declarations made using C-style syntax, with the array indicator attached to the variable,
 rather than Java-style syntax, with the array indicator attached to the type.
+<!-- tooltip end -->
 <p>
 <small>Powered by InspectionGadgets</small>
 </body>
@@ -12,6 +12,7 @@ here (introduced in Java 5), which will cache objects for values between -128 an
 <p>
 This inspection only reports if the project or module is configured to use a
 language level of 5.0 or higher.
+<!-- tooltip end -->
 <p>
 <small>Powered by InspectionGadgets</small>
 </body>
@@ -3,6 +3,7 @@
 This inspection reports any to methods declared <b>native</b> while in
 a synchronized block or method. While not necessarily representing a problem, such calls cause
 an expensive context switch, and are best kept out of synchronized contexts, if possible.
+<!-- tooltip end -->
 <p>
 <small>Powered by InspectionGadgets</small>
 </body>
@@ -5,6 +5,7 @@ A simple property getter is defined as one which simply returns the value of a f
 and does no other calculation. Such simple getter calls may be safely inlined, at a small performance
 improvement. Some coding standards also suggest against the use of simple getters for code clarity
 reasons.
+<!-- tooltip end -->
 <p>
 Use the first option below to only report on getter calls on <b>this</b>, not on objects of the same type passed in as a parameter. Use
 the second option below to only report when the getter is <b>private</b>.
@@ -5,6 +5,7 @@ A simple property setter is defined as one which simply assigns the value of its
 and does no other calculation. Such simple setter calls may be safely inlined, at a small performance
 improvement. Some coding standards also suggest against the use of simple setters for code clarity
 reasons.
+<!-- tooltip end -->
 <p>
 Use the first option below to only report on setter calls on <b>this</b>, not on objects of the same type passed in as a parameter. Use
 the second option below to only report when the setter is <b>private</b>.
@@ -4,6 +4,7 @@ This inspection reports calls to the <b>concat</b> method
 of a <b>java.lang.String</b> object. Such calls can be
 replaced with the '+' operator for increased code clarity and possible increased
 performance if the method was invoked on a constant with a constant argument.
+<!-- tooltip end -->
 <p>
 <small>Powered by InspectionGadgets</small>
 </body>
@@ -4,6 +4,7 @@ This inspection reports type cast expressions which are surrounded by an
 <b>instanceof</b> check for a different type.
 While it is possible that this was intended, such a construct is most likely an error, and will
 result in a <b>java.lang.ClassCastException</b> at runtime.
+<!-- tooltip end -->
 <p>
 <small>Powered by InspectionGadgets</small>
 </body>
@@ -3,6 +3,7 @@
 This inspection reports any cast operations between built-in numeric types which may
 result in loss of precision. Such casts are not necessarily a problem, but may result in difficult to
 trace bugs if the loss of precision is unexpected.
+<!-- tooltip end -->
 <p>
 Use the checkbox below to indicate that this inspection should ignore casts from
 <b>int</b> to <b>char</b>.
@@ -3,6 +3,7 @@
 This inspection reports casting a value to a concrete class, rather than an interface.
 Such declarations may represent a failure of abstraction, and may make testing more difficult.
 Declarations whose classes come from system or third-party libraries will not be reported by this inspection.
+<!-- tooltip end -->
 <p>
 Use the checkbox below to have this inspection ignore casts to abstract classes.
 <p>
@@ -5,6 +5,7 @@ the cast type is an interface, and the cast expression has a class type which ne
 implements the cast interface, nor has any visible subclasses which implement or extend the cast interface.
 While it is possible that this was intended, such a construct is most likely an error, and will
 result in a <b>java.lang.ClassCastException</b> at runtime.
+<!-- tooltip end -->
 <p>
 <small>Powered by InspectionGadgets</small>
 </body>
@@ -4,6 +4,7 @@ This inspection reports any <b>catch</b> block where
 the caught exception is immediately rethrown, without performing any action on it.
 Such <b>catch</b> blocks are unnecessary or lack error
 handling.
+<!-- tooltip end -->
 <p>
 <small>Powered by InspectionGadgets</small>
 </body>
@@ -2,6 +2,7 @@
 <body>
 This inspection reports chained equality comparisons (i.e. <b>a==b==c</b>).
 Such comparisons are confusing.
+<!-- tooltip end -->
 <p>
 <small>Powered by InspectionGadgets</small>
 </body>
@@ -2,6 +2,7 @@
 <body>
 This inspection reports method calls whose target is another
 method call.
+<!-- tooltip end -->
 <p>
 <small>Powered by InspectionGadgets</small>
 </body>
@@ -6,6 +6,7 @@ front of a <b>try</b> block and closed in the corresponding
 if an exception is thrown before the resource is closed. Channel resources reported
 by this inspection include any instances created by calling
 <b>getChannel()</b> on a file or socket resource.
+<!-- tooltip end -->
 <p>
 Use the checkbox below to specify if a Channel is allowed to be opened inside a try
 block. This style is less desirable because it is more verbose than opening a Channel
@@ -1,7 +1,8 @@
 <html>
 <body>
 This inspection reports on any expressions of type char which are used in
-addition or substraction expressions.
+addition or subtraction expressions.
+<!-- tooltip end -->
 <p>
 <small>Powered by InspectionGadgets</small>
 </body>
@@ -2,6 +2,7 @@
 <body>
 This inspection reports any ordinal comparison of <b>char</b> values. In an internationalized
 environment, such comparisons are rarely correct.
+<!-- tooltip end -->
 <p>
 <small>Powered by InspectionGadgets</small>
 </body>
@@ -7,6 +7,7 @@ This inspection reports large array allocations which do not check
 for <b>java.lang.OutOfMemoryError</b>. In memory
 constrained environments, allocations of large data objects should probably
 be checked for memory depletion.
+<!-- tooltip end -->
 <p>
 Use the field below to specify the maximum number of elements to allow in
 unchecked array allocations.
@@ -3,6 +3,7 @@
 This inspection reports checked exception classes (i.e. subclasses of <b>Exception</b> which are
 not also subclasses of <b>RuntimeException</b>). Certain coding standards require that all user-defined exception
 classes be unchecked.
+<!-- tooltip end -->
 <p>
 <small>Powered by InspectionGadgets</small>
 </body>
@@ -4,6 +4,7 @@ This inspection reports class with too high of a total complexity. The
 total complexity of a class is the sum of the cyclomatic complexities of all the methods
 and initializers the class declares. Inherited methods and initializers are not counted
 toward the total complexity.
+<!-- tooltip end -->
 <p>
 Use the field provided below to specify the maximum acceptable complexity a class might have.
 <p>
@@ -4,6 +4,7 @@ This inspection reports classes which are highly coupled, i.e. that reference to
 Classes with too high a coupling can be very fragile, and should probably be broken up. References to system classes
 (those in the <b>java.</b>or <b>javax.</b> packages), are not
 counted for purposes of this inspection.
+<!-- tooltip end -->
 <p>
 Use the field provided below to specify the maximum acceptable coupling a class might have.
 <p>
@@ -5,6 +5,7 @@ be used outside the class's stated scope. For instance, this inspection would re
 a public method which returns a private inner class, or a protected field whose
 type is a package-visible class. While legal Java, such references can be very
 confusing, and make reuse difficult.
+<!-- tooltip end -->
 <p>
 <small>Powered by InspectionGadgets</small>
 </body>
@@ -1,7 +1,7 @@
 <html>
 <body>
-This inspection reports any classes
-which do not contain package declarations.
+This inspection reports any classes which do not contain package declarations.
+<!-- tooltip end -->
 <p>
 <small>Powered by InspectionGadgets</small>
 </body>
@@ -3,6 +3,7 @@
 This inspection reports any classes which are neither dependent on nor depended on by other classes
 in their module. Such classes are an indication of ad-hoc or incoherent modularisation strategies,
 and may often profitably be moved.
+<!-- tooltip end -->
 <p>
 <small>New in 11, Powered by InspectionGadgets</small>
 </body>
@@ -3,6 +3,7 @@
 This inspection reports class too deep in the inheritance hierarchy. Classes too deeply inherited
 may be confusing, and are a good sign that refactoring may be necessary. This inspection counts all superclasses
 from a library as a single superclass (libraries are considered unmodifyable).
+<!-- tooltip end -->
 <p>
 Use the field provided below to specify the maximum acceptable inheritance depth a class might have.
 <p>
@@ -5,6 +5,7 @@ in classes. Some coding standards prohibit such initializers, preferring initial
 in constructors or field initializers. Non-<b>static</b> initializers
 may also be inadvertently created by deleting the <b>static</b> keyword,
 resulting in obscure bugs.
+<!-- tooltip end -->
 <p>
 <small>Powered by InspectionGadgets</small>
 </body>
@@ -3,6 +3,7 @@
 This inspection reports any class initializers which may safely be made <b>static</b>.
 A class initializer may be static if it does not reference any of its class' non static methods
 and non static fields.
+<!-- tooltip end -->
 <p>
 <small>Powered by InspectionGadgets</small>
 </body>
@@ -2,6 +2,7 @@
 <body>
 This inspection reports any instantiations of <b>java.lang.ClassLoader</b> objects.
 While often benign, any instantiations to <b>ClassLoader</b> should be closely examined in any security audit.
+<!-- tooltip end -->
 <p>
 <small>Powered by InspectionGadgets</small>
 </body>
@@ -5,6 +5,7 @@ which may be simplified to be interfaces. This occurs if the class has no superc
 than Object), has no fields declared that are not <b>static</b>, <b>final</b>, and <b>public</b>, and has no
 methods declared that are not <b>public</b> and <b>abstract</b>, and no inner classes
 that cannot themselves be interfaces.
+<!-- tooltip end -->
 <p>
 <small>Powered by InspectionGadgets</small>
 </body>
@@ -4,6 +4,7 @@ This inspection reports top-level class names which do not match the name of
 their containing file. While the Java specification allows such naming for non-<b>public</b> classes,
 such misnamed files can be confusing, and may degrade the usefulness of various
 software tools.
+<!-- tooltip end -->
 <p>
 <small>Powered by InspectionGadgets</small>
 </body>
@@ -3,6 +3,7 @@
 This inspection reports classes whose names are prefixed with their package names, irrespective of
 capitalization. While occasionally reasonable, this is often due to a poor naming scheme, and may be redundant and
 annoying.
+<!-- tooltip end -->
 <p>
 <small>Powered by InspectionGadgets</small>
 </body>
@@ -2,6 +2,7 @@
 <body>
 This inspection reports class being named identically to one of their
 super classes (but in different packages). Such class name may be very confusing.
+<!-- tooltip end -->
 <p>
 <small>Powered by InspectionGadgets</small>
 </body>
@@ -2,6 +2,7 @@
 <body>
 This inspection reports classes whose names are either too short, too long, or do not follow
 the specified regular expression pattern.
+<!-- tooltip end -->
 <p>
 Use the fields provided below to specify minimum length, maximum length and regular expression expected for class names.
 (Regular expressions are in standard <b>java.util.regex</b> format.)
@@ -2,6 +2,7 @@
 <body>
 This inspection reports inner classes too deeply nested. Nesting inner classes inside
 inner classes is almost certain to be confusing, and is a good sign that refactoring may be necessary.
+<!-- tooltip end -->
 <p>
 Use the field provided below to specify the maximum acceptable nesting depth a class might have.
 <p>
@@ -9,6 +9,7 @@ would otherwise be performed by the compiler. Replacing such a method call with
 a call to the <b>java.lang.reflect.Constructor.newInstance()</b>
 method avoids this problem by wrapping any exception thrown by the constructor
 in a <b>java.lang.reflect.InvocationTargetException</b>.
+<!-- tooltip end -->
 <p>
 <small>Powered by InspectionGadgets</small>
 </body>
@@ -3,6 +3,7 @@
 This inspection reports any classes which is only depended on and only depends on one module which
 is different from the module containing the class. Such class could be moved into
 that module.
+<!-- tooltip end -->
 <p>
 <small>New in 11, Powered by InspectionGadgets</small>
 </body>
@@ -3,6 +3,7 @@
 This inspection reports any classes which is only depended on and only depends on one module which
 is different from the module containing the class. Such class could be moved into
 that module.
+<!-- tooltip end -->
 <p>
 <small>New in 11, Powered by InspectionGadgets</small>
 </body>
@@ -2,6 +2,7 @@
 <body>
 This inspection reports classes which contain references to one of their subclasses.
 Such references may be confusing, and violate several rules of object-oriented design.
+<!-- tooltip end -->
 <p>
 <small>Powered by InspectionGadgets</small>
 </body>
@@ -3,6 +3,7 @@
 This inspection reports any classes which are neither dependent on nor depended on by other classes
 in their package. Such classes are an indication of ad-hoc or incoherent packaging strategies,
 and may often profitably be moved.
+<!-- tooltip end -->
 <p>
 <small>Powered by InspectionGadgets</small>
 </body>
@@ -5,6 +5,7 @@ other classes in the project. Such classes may be prone to instability, as modif
 to any of the classes it is dependent on may require changing the class. Only top-level
 classes are reported by this inspection. Since this inspection requires global code
 analysis, it is only available in batch inspection mode.
+<!-- tooltip end -->
 <p>
 Use the field below to specify the maximum number of dependencies a class may have
 before triggering this inspection
@@ -4,6 +4,7 @@ This global inspection reports any classes on which too many other classes in yo
 are directly dependent. Such classes may be expensive to modify, as changes to the class may
 require changing many other classes. Only top-level classes are reported by this inspection.
 Since this inspection requires global code analysis, it is only available in batch inspection mode.
+<!-- tooltip end -->
 <p>
 Use the field below to specify the maximum number of dependents a class may have before
 triggering this inspection
@@ -5,6 +5,7 @@ on too many other classes in your project. Such classes may be prone to instabil
 as changes to any of the classes it is dependent on may require changing the class.
 Only top-level classes are reported by this inspection.
 Since this inspection requires global code analysis, it is only available in batch inspection mode.
+<!-- tooltip end -->
 <p>
 Use the field below to specify the maximum number of direct or indirect dependencies
 a class may have before triggering this inspection
--- a/Show More
+++ b/Show More