Posted under Angular & PrimeNG & Uncategorized & Web
Permalink
Tags Tip, Tutorial
My initial attempt on this was to use static positioning when the title bar was unpinned (e.g. scrollable), and fixed positioning when the bar was pinned.
When using fixed positioning as above, the title bar is no longer in the normal flow so the rest of the content (in my case, encapsulated in a main container div) will sit underneath the title bar. I therefore used a top margin when pinned to prevent the top of the content being hidden. Some issues arose with this as follows:
1/ It was necessary therefore to add an additional margin to the main container to avoid occluding the content under the title bar, which meant exactly knowing its height. In addition, to allow a gap between the title bar and the content when pinned, I added a border to the title bar of the same colour as the page background, in effect to act as a kind of margin. This worked fine.
1/ My title bar was floated, so it automatically resized to fit its content. this meant that the margin allowance on the main content div would have to vary dynamically on resize.
2/ One way around this was to set media query breakpoints to trigger on the resize, and to set a fixed height for the title bar rather than floating it, and setting the margin on the content to match in each media query. In addition to this, I implemented a flexbox solution where the container was sized and the content centered within it. I was not so keen on this as it lost the ability to dynamically resize the title bar container as needed by the content resizing, and might cause problems if the layout/text changed in the title bar for example.
3/ Another way was to use a resize event and change the size of the margin on the content programmatically, using an rxjs debounced resize event. This worked pretty well, but I needed to switch the content margin on and off when the title bar was pinned/unpinned. This should have worked ok, but I noticed some slight visual movements in some page elements on pinning change, even though I could not see any style or layout changes in the browser inspector. This was annoying.
4/ I then tried using absolute positioning of the title bar when unpinned, and fixed positioning when pinned. This relied on using the same programmatic margin on the content for both, and in fact simplified the code, as I did not have to switch off the programmatic margin change when unpinning the title bar – it was used all the time, as absolute positioning was also outside the normal flow. Also, the slight glitches I saw on the page were completely eliminated.
I therefore stuck with method 4/ as the final solution. Some sample code showing the programmatic resize is as follows:-
private readonly resizeDebounceTime = 100;
private resizeObservable!: Observable<Event>;
private resizeSubscription!: Subscription;
private readonly formatPixelSize = (pixels: number) => `${pixels}px`;…
ngAfterViewInit(): void {
this.initBannerSpacingAdjustment();
}ngOnDestroy(): void {
this.destroyBannerSpacingAdjustment();
}
private initBannerSpacingAdjustment(): void {
this.adjustBannerSpacing();
this.resizeObservable = fromEvent(window,
‘resize’).pipe(debounceTime(this.resizeDebounceTime));
this.resizeSubscription = this.resizeObservable.subscribe(event =>
this.adjustBannerSpacing());
}private destroyBannerSpacingAdjustment(): void {
if (this.resizeSubscription) {
this.resizeSubscription.unsubscribe();
}
}private adjustBannerSpacing(): void {
/* note that the offsetHeight is the total height of the banner,
* including padding and border */
this.mainContainer.nativeElement.style.marginTop =
this.formatPixelSize(this.banner.nativeElement.offsetHeight);
}
Comments Off on Pinning a title bar on a page with Angular 11/PrimeNG 11