HTML source code, style-sheets, scripts, and images for deployment on mingw.osdn.io
Revision | 2364afc57ab7ca2ddafe75845885ef2330cc7f4b (tree) |
---|---|
Time | 2020-11-06 19:12:24 |
Author | Keith Marshall <keith@user...> |
Commiter | Keith Marshall |
Correctly handle internal page section references.
* 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".
@@ -171,7 +171,8 @@ project mailing lists available | ||
171 | 171 | subscription to these older lists is no longer permitted. |
172 | 172 | </p> |
173 | 173 | <hr /> |
174 | -<h3 id="cross-compile">Using MinGW for Cross-Hosted Development</h3> | |
174 | +<div class="overlapped" id="cross-compile"> | |
175 | +<h3>Using MinGW for Cross-Hosted Development</h3> | |
175 | 176 | <p>While <strong>MinGW</strong> provides tools |
176 | 177 | primarily intended for use by developers working on the |
177 | 178 | MS‑Windows platform, |
@@ -188,6 +189,6 @@ although we may be able to help out with advice related to the specifics | ||
188 | 189 | of MS‑Windows applications development, |
189 | 190 | common to the use of our own native tool chains |
190 | 191 | and to such cross‑compilers. |
191 | -</p> | |
192 | +</p></div><!-- cross-compile --> | |
192 | 193 | |
193 | 194 | <!-- $RCSfile$: end of file --> |
@@ -78,7 +78,7 @@ in any way, affiliated with MinGW.org; | ||
78 | 78 | MinGW.org <strong>does not</strong> support the products |
79 | 79 | of these projects.</em> |
80 | 80 | </p> |
81 | -<div id="general-enquiry"> | |
81 | +<div class="overlapped" id="general-enquiry"> | |
82 | 82 | <h3>General Enquiries</h3> |
83 | 83 | <p>If you encounter a problem using MinGW, or MSYS, |
84 | 84 | and you cannot find a satisfactory answer on our web‑site, |
@@ -111,7 +111,7 @@ we <em>strongly</em> recommend that you acquaint yourself with | ||
111 | 111 | compliance with this may improve your chances of receiving a response, |
112 | 112 | whereas non‑compliance may result in your post being ignored. |
113 | 113 | </p></div><!-- general-enquiry --> |
114 | -<div id="bug-report"> | |
114 | +<div class="overlapped" id="bug-report"> | |
115 | 115 | <h3>Reporting Bugs</h3> |
116 | 116 | <p>After discussing an issue on the mailing‑list, |
117 | 117 | as described above, you may be asked to file a formal bug report. |
@@ -185,7 +185,7 @@ and create a bad impression of the reporter). | ||
185 | 185 | Finally, when you are satisfied, click the “Submit” button |
186 | 186 | to complete the ticket submission process. |
187 | 187 | </p></div><!-- bug-report --> |
188 | -<div id="feature-request"> | |
188 | +<div class="overlapped" id="feature-request"> | |
189 | 189 | <h3>Feature Requests</h3> |
190 | 190 | <p>When you wish to request the implementation of a new feature, |
191 | 191 | (e.g. to support a currently unsupported MSVC or POSIX API function), |
@@ -74,7 +74,7 @@ today, only two remain operational, and both are | ||
74 | 74 | <p>The currently operational |
75 | 75 | MinGW.org mailing‑lists are:— |
76 | 76 | </p> |
77 | -<dl class="no-indent" id="mingw-users"> | |
77 | +<dl class="no-indent overlapped" id="mingw-users"> | |
78 | 78 | <dt><a rel="noopener noreferrer" target="_blank" |
79 | 79 | href="https://lists.osdn.me/mailman/listinfo/mingw-users" |
80 | 80 | >MinGW‑Users Mailing‑List</a> |
@@ -133,7 +133,7 @@ and the SourceForge.net (lower box) archives, respectively. | ||
133 | 133 | <input type="hidden" name="mailing_list" value="mingw-users" /> |
134 | 134 | </form> |
135 | 135 | </dd> |
136 | -</dl><dl class="no-indent" id="mingw-notify"> | |
136 | +</dl><dl class="no-indent overlapped" id="mingw-notify"> | |
137 | 137 | <dt><a rel="noopener noreferrer" target="_blank" |
138 | 138 | href="https://lists.osdn.me/mailman/listinfo/mingw-notify" |
139 | 139 | >MinGW‑Notify Mailing‑List</a> |
@@ -186,7 +186,7 @@ However, archives of historical postings remain | ||
186 | 186 | and may be searched using their respective keyword‑search boxes, |
187 | 187 | below. |
188 | 188 | </p> |
189 | -<dl class="no-indent" id="mingw-msys"> | |
189 | +<dl class="no-indent overlapped" id="mingw-msys"> | |
190 | 190 | <dt><a rel="noopener noreferrer" target="_blank" |
191 | 191 | href="https://sourceforge.net/p/mingw/mailman/mingw-msys" |
192 | 192 | >MinGW‑MSYS Mailing‑List</a> |
@@ -245,7 +245,7 @@ on the historical MinGW-CVS archive. | ||
245 | 245 | </form> |
246 | 246 | </dd> |
247 | 247 | </dl> |
248 | -<div id="list-etiquette"> | |
248 | +<div class="overlapped" id="list-etiquette"> | |
249 | 249 | <h3>Mailing‑List Posting Etiquette</h3> |
250 | 250 | <p>MinGW is an open source project. |
251 | 251 | As such, it is heavily dependent on people who dedicate |
@@ -255,6 +255,30 @@ dl.masthead+p | ||
255 | 255 | } |
256 | 256 | |
257 | 257 | |
258 | +/* Subsection Reference Positioning Relative to Page Header | |
259 | + * ======================================================== | |
260 | + */ | |
261 | +.overlapped | |
262 | +{ /* Any internal page reference will be positioned at the same | |
263 | + * vertical offset, within the viewport, as the top of the page | |
264 | + * header block. Thus, any text which appears within the upper | |
265 | + * 70px of the subsection division will be hidden behind the | |
266 | + * header block; adjust the alignment of the target element, | |
267 | + * such that its top margin overlaps the lower region of the | |
268 | + * preceding element, by the depth of the header block, then | |
269 | + * pad it, to push the content downward, into the viewport. | |
270 | + */ | |
271 | + margin-top: -70px; padding-top: 70px; | |
272 | +} | |
273 | +hr+div.overlapped | |
274 | +{ /* When an overlapped division follows a horizontal rule, we | |
275 | + * need to adjust its position upward, to allow for the blank | |
276 | + * space in the bottom margin of the rule element. | |
277 | + */ | |
278 | + margin-top: calc( -70px - 0.6em ); | |
279 | +} | |
280 | + | |
281 | + | |
258 | 282 | /* Supplementary Formatting for Sections with Numbered Headings |
259 | 283 | * ============================================================ |
260 | 284 | */ |
@@ -73,6 +73,11 @@ function load_content( container, src ) | ||
73 | 73 | update_page_content_header( "title" ); |
74 | 74 | update_page_content_header( "subtitle" ); |
75 | 75 | set_content( "e404-missing-page", document.URL ); |
76 | + if( src.includes("#") ) | |
77 | + { src = src.substring( src.indexOf("#") + 1, src.length ); | |
78 | + element = document.getElementById( src ); | |
79 | + if( element ) element.scrollIntoView(); | |
80 | + } | |
76 | 81 | break; |
77 | 82 | case 404: |
78 | 83 | load_content( container, "missing.html" ); |