How to generate your free kundli in mins

How to generate your free kundli in mins

A
Admin
General
Jan 28, 2024  |  92 Views  |  2 min read

Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry's standard dummy text ever since the 1500s, when an unknown printer took a galley of type and scrambled it to make a type specimen book. It has survived not only five centuries, but also the leap into electronic typesetting, remaining essentially unchanged. It was popularised in the 1960s with the release of Letraset sheets containing Lorem Ipsum passages, and more recently with desktop publishing software like Aldus PageMaker including versions of Lorem Ipsum.

 

Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry's standard dummy text ever since the 1500s, when an unknown printer took a galley of type and scrambled it to make a type specimen book. It has survived not only five centuries, but also the leap into electronic typesetting, remaining essentially unchanged. It was popularised in the 1960s with the release of Letraset sheets containing Lorem Ipsum passages, and more recently with desktop publishing software like Aldus PageMaker including versions of Lorem Ipsum.

 

Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry's standard dummy text ever since the 1500s, when an unknown printer took a galley of type and scrambled it to make a type specimen book. It has survived not only five centuries, but also the leap into electronic typesetting, remaining essentially unchanged. It was popularised in the 1960s with the release of Letraset sheets containing Lorem Ipsum passages, and more recently with desktop publishing software like Aldus PageMaker including versions of Lorem Ipsum.

 

Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry's standard dummy text ever since the 1500s, when an unknown printer took a galley of type and scrambled it to make a type specimen book. It has survived not only five centuries, but also the leap into electronic typesetting, remaining essentially unchanged. It was popularised in the 1960s with the release of Letraset sheets containing Lorem Ipsum passages, and more recently with desktop publishing software like Aldus PageMaker including versions of Lorem Ipsum.

Back to Blog Top of Article
Online <?php echo e($appName); ?> Consultation, Ask an Astrologer - Astroway
Found it — the bug is a timing issue with hidden elements, and it explains why local "looks perfect" while live doesn't (timing is non-deterministic, so it's really just luck either way). Root cause javascript This runs initGoogleAuthButton() the moment the Google script finishes loading — which is almost immediately on page load, before the user has even opened the login modal. But your modal starts hidden: css .modal-overlay { display: none; ... } An element with display: none (or a hidden ancestor) always reports offsetWidth = 0. So: javascript width: container.offsetWidth, // reads 0 when the modal hasn't been opened yet Google then falls back to its own default minimum button width instead of matching your container — which is exactly the shrunk-looking button you're seeing. On local it likely "worked" purely by coincidence of load timing, network speed, or you happening to open the modal slowly enough for something to re-trigger — not because the code was actually correct. Fix — render the Google button only when the modal is actually opened, not on page load Since showLoginModal() lives in auth_system.js (which you haven't shared), the safest fix that doesn't require touching that file is to watch for the modal's active class being added, and render the button at that moment — when its real width is available. Replace your current Google script block with this: html