58f9a8971053e464cfefcfff018e491cae5dd8f3
dschmelt
  Mon Aug 30 11:27:36 2021 -0700
Setting width of Tables at b0b's request No RM

diff --git src/hg/makeDb/trackDb/human/dbSnp153Composite.html src/hg/makeDb/trackDb/human/dbSnp153Composite.html
index 4565c43..09a717b 100644
--- src/hg/makeDb/trackDb/human/dbSnp153Composite.html
+++ src/hg/makeDb/trackDb/human/dbSnp153Composite.html
@@ -186,31 +186,31 @@
     <li>assorted features and anomalies noted by UCSC during processing of dbSNP's data
     </li>
   </ul>
 </p>
 
 <a name="ucscNotes">
 <h3>Interesting and anomalous conditions noted by UCSC</h3>
 <p>
 While processing the information downloaded from dbSNP,
 UCSC annotates some properties of interest.
 These are noted on the item details page,
 and may be useful to include or exclude affected variants.
 </p><p>
 Some are purely informational:
 </p>
-<table class="descTbl">
+<table style="width:1250px" class="descTbl">
   <tr><th>keyword in data file (dbSnp153.bb)</th>
     <th># in hg19</th><th># in hg38</th><th>description</th></tr>
   <tr>
     <td>clinvar</td>
     <td class="number">454678</td>
     <td class="number">453996</td>
     <td>Variant is in ClinVar.</td>
   </tr>
   <tr>
     <td>clinvarBenign</td>
     <td class="number">143864</td>
     <td class="number">143736</td>
     <td>Variant is in ClinVar with clinical significance of benign and/or likely benign.</td>
   </tr>
   <tr>
@@ -272,31 +272,31 @@
       in some, but not all, projects reporting frequencies, or has no frequency data.</td>
   </tr>
   <tr>
     <td>revStrand</td>
     <td class="number">3813702</td>
     <td class="number">4532511</td>
     <td>Alleles are displayed on the + strand at the current position.
       dbSNP's alleles are displayed on the + strand of a different assembly sequence,
       so dbSNP's variant page shows alleles that are reverse-complemented with respect to
       the alleles displayed above.</td>
   </tr>
 </table>
 <p>
 while others may indicate that the reference genome contains a rare variant or sequencing issue:
 </p>
-<table class="descTbl">
+<table style="width:1250px" class="descTbl">
   <tr><th>keyword in data file (dbSnp153.bb)</th>
     <th># in hg19</th><th># in hg38</th><th>description</th></tr>
   <tr>
     <td>refIsAmbiguous</td>
     <td class="number">101</td>
     <td class="number">111</td>
     <td>The reference genome allele contains an IUPAC ambiguous base
       (e.g. 'R' for 'A or G', or 'N' for 'any base').</td>
   </tr>
   <tr>
     <td>refIsMinor</td>
     <td class="number">3272116</td>
     <td class="number">3360435</td>
     <td>The reference genome allele is not the major allele in at least one project.</td>
   </tr>
@@ -313,31 +313,31 @@
     <td>The reference genome allele has never been observed in a population sequencing project
       reporting frequencies.</td>
   </tr>
   <tr>
     <td>refMismatch</td>
     <td class="number">4</td>
     <td class="number">33</td>
     <td>The reference genome allele reported by dbSNP differs from the GenBank assembly sequence.
       This is very rare and in all cases observed so far, the GenBank assembly has an 'N'
       while the RefSeq assembly used by dbSNP has a less ambiguous character such as 'R'.</td>
   </tr>
 </table>
 <p>
 and others may indicate an anomaly or problem with the variant data:
 </p>
-<table class="descTbl">
+<table style="width:1250px" class="descTbl">
   <tr><th>keyword in data file (dbSnp153.bb)</th>
     <th># in hg19</th><th># in hg38</th><th>description</th></tr>
   <tr>
     <td>altIsAmbiguous</td>
     <td class="number">10755</td>
     <td class="number">10888</td>
     <td>At least one alternate allele contains an IUPAC ambiguous base (e.g. 'R' for 'A or G').
       For alleles containing more than one ambiguous base, this may create a
       combinatoric explosion of possible alleles.</td>
   </tr>
   <tr>
     <td>classMismatch</td>
     <td class="number">5998</td>
     <td class="number">6216</td>
     <td>Variation class/type is inconsistent with alleles mapped to this genome assembly.</td>