* site.js (load_content) ["#" in URL]: Scroll to internal reference.
* site.css (overlapped): New styling class; define it, such that any
element to which it is assigned will be positioned, with its topmost
content fully visible below the page header block, when an internal
page reference is scrolled into view.
* contact.html (general-enquiry, bug-report, feature-request)
* mailing.html (mingw-users, mingw-notify, mingw-msys, list-etiquette)
* about.html (cross-compile): Mark reference points as "overlapped".
subscription to these older lists is no longer permitted.
</p>
<hr />
-<h3 id="cross-compile">Using MinGW for Cross-Hosted Development</h3>
+<div class="overlapped" id="cross-compile">
+<h3>Using MinGW for Cross-Hosted Development</h3>
<p>While <strong>MinGW</strong> provides tools
primarily intended for use by developers working on the
MS‑Windows platform,
of MS‑Windows applications development,
common to the use of our own native tool chains
and to such cross‑compilers.
-</p>
+</p></div><!-- cross-compile -->
<!-- $RCSfile$: end of file -->
MinGW.org <strong>does not</strong> support the products
of these projects.</em>
</p>
-<div id="general-enquiry">
+<div class="overlapped" id="general-enquiry">
<h3>General Enquiries</h3>
<p>If you encounter a problem using MinGW, or MSYS,
and you cannot find a satisfactory answer on our web‑site,
compliance with this may improve your chances of receiving a response,
whereas non‑compliance may result in your post being ignored.
</p></div><!-- general-enquiry -->
-<div id="bug-report">
+<div class="overlapped" id="bug-report">
<h3>Reporting Bugs</h3>
<p>After discussing an issue on the mailing‑list,
as described above, you may be asked to file a formal bug report.
Finally, when you are satisfied, click the “Submit” button
to complete the ticket submission process.
</p></div><!-- bug-report -->
-<div id="feature-request">
+<div class="overlapped" id="feature-request">
<h3>Feature Requests</h3>
<p>When you wish to request the implementation of a new feature,
(e.g. to support a currently unsupported MSVC or POSIX API function),
<p>The currently operational
MinGW.org mailing‑lists are:—
</p>
-<dl class="no-indent" id="mingw-users">
+<dl class="no-indent overlapped" id="mingw-users">
<dt><a rel="noopener noreferrer" target="_blank"
href="https://lists.osdn.me/mailman/listinfo/mingw-users"
>MinGW‑Users Mailing‑List</a>
<input type="hidden" name="mailing_list" value="mingw-users" />
</form>
</dd>
-</dl><dl class="no-indent" id="mingw-notify">
+</dl><dl class="no-indent overlapped" id="mingw-notify">
<dt><a rel="noopener noreferrer" target="_blank"
href="https://lists.osdn.me/mailman/listinfo/mingw-notify"
>MinGW‑Notify Mailing‑List</a>
and may be searched using their respective keyword‑search boxes,
below.
</p>
-<dl class="no-indent" id="mingw-msys">
+<dl class="no-indent overlapped" id="mingw-msys">
<dt><a rel="noopener noreferrer" target="_blank"
href="https://sourceforge.net/p/mingw/mailman/mingw-msys"
>MinGW‑MSYS Mailing‑List</a>
</form>
</dd>
</dl>
-<div id="list-etiquette">
+<div class="overlapped" id="list-etiquette">
<h3>Mailing‑List Posting Etiquette</h3>
<p>MinGW is an open source project.
As such, it is heavily dependent on people who dedicate
}
+/* Subsection Reference Positioning Relative to Page Header
+ * ========================================================
+ */
+.overlapped
+{ /* Any internal page reference will be positioned at the same
+ * vertical offset, within the viewport, as the top of the page
+ * header block. Thus, any text which appears within the upper
+ * 70px of the subsection division will be hidden behind the
+ * header block; adjust the alignment of the target element,
+ * such that its top margin overlaps the lower region of the
+ * preceding element, by the depth of the header block, then
+ * pad it, to push the content downward, into the viewport.
+ */
+ margin-top: -70px; padding-top: 70px;
+}
+hr+div.overlapped
+{ /* When an overlapped division follows a horizontal rule, we
+ * need to adjust its position upward, to allow for the blank
+ * space in the bottom margin of the rule element.
+ */
+ margin-top: calc( -70px - 0.6em );
+}
+
+
/* Supplementary Formatting for Sections with Numbered Headings
* ============================================================
*/
update_page_content_header( "title" );
update_page_content_header( "subtitle" );
set_content( "e404-missing-page", document.URL );
+ if( src.includes("#") )
+ { src = src.substring( src.indexOf("#") + 1, src.length );
+ element = document.getElementById( src );
+ if( element ) element.scrollIntoView();
+ }
break;
case 404:
load_content( container, "missing.html" );