PageSourceSearch

https://www.jitterbit.com/wp-content/plugins/header-footer-custom-…/js/header-footer-custom-html-public.js

js jitterbit.com collected 2026-10-02 03:01:19 UTC 1,280 bytes, 48 lines download raw bytes

1/**
2 * All of the js for your public-facing functionality should be
3 * included in this file.
4 *
5 * @link              https://www.enweby.com/
6 * @since             1.0.0
7 * @package           Header_Footer_Custom_Html
8 */
9
10(function( $ ) {
11	'use strict';
12
13	/**
14	 * All of the code for your public-facing JavaScript source
15	 * should reside in this file.
16	 *
17	 * Note: It has been assumed you will write jQuery code here, so the
18	 * $ function reference has been prepared for usage within the scope
19	 * of this function.
20	 *
21	 * This enables you to define handlers, for when the DOM is ready:
22	 *
23	 * $(function() {
24	 *
25	 * });
26	 *
27	 * When the window is loaded:
28	 *
29	 * $( window ).load(function() {
30	 *
31	 * });
32	 *
33	 * ...and/or other possibilities.
34	 *
35	 * Ideally, it is not considered best practise to attach more than a
36	 * single DOM-ready or window-load handler for a particular page.
37	 * Although scripts in the WordPress core, Plugins and Themes may be
38	 * practising this, we should strive to set a better example in our own work.
39	 */
40	$(
41		function() {
42			$( "#page" ).css( 'margin-top', $( ".enweby-hfch-sticky-header-top" ).height() + 'px' );
43			$( "#page" ).css( 'margin-bottom', $( ".enweby-hfch-sticky-footer-bottom" ).height() + 'px' );
44
45		}
46	);
47
48})( jQuery );

Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.