Bell_Internet page: address bar in top banner does not load (JavaScript error)

vasigorc
Contributor

Page: https://www.bell.ca/Bell_Internet
Browser: Chrome 155, Linux

Problem: The "Enter your address" bar in the top banner does not appear. I cannot check availability from it.

Console errors on page load:

  • "ReferenceError: pca is not defined" at "new InlineQualification" (bundles.js)
  • "TypeError: Failed to execute 'observe' on 'MutationObserver': parameter 1 is not of type 'Node'" (bundles.js)
  • "SyntaxError: Unexpected end of input" (inline script in the page, around line 7504)

Likely cause: The Network tab shows that the Canada Post AddressComplete script (addresscomplete-2.30.min.js) starts to load about 1 second after DOMContentLoaded. The address bar code seems to need the "pca" object from that script before the script is ready.

Workaround: The "enter your address" link under "Featured Internet plans" opens a Check availability pop-up. That pop-up works.

Can you please pass this to the web team?

0 3 33
3 REPLIES 3

BellPatricia
Moderator

Good evening @vasigorc 

Welcome to the Bell community and thank you for flagging this to us 🙂

We would just like to gather a few more details that could help us investigate further.

  • Does the same issue occur in another browser?
  • Can you reproduce this consistently, or does it happen intermittently?
  • Has this issue been happening for a while, or did it start today?
  • Are you able to test on another device?

Looking forward to your reply,

@BellPatricia 

vasigorc
Contributor

Thanks, Patricia.

Other browser: I tested only on Chrome, Version 155.0.8059.84 (Official Build) (x86_64). I will not test other browsers. Chrome is the most used browser in Canada (about 49% of all traffic, 58% on desktop, per Statcounter). Cross-browser testing is work for your development team.

Consistent or intermittent: Consistent. The error occurs on every page load.

Since when: I first saw it on November 18.

Other device: I will not test on another device.

This is not a browser problem. It is a load-order problem in the page code: the address bar code runs before the Canada Post script loads. The console errors in my first post show this. Please send them to the web team.

Vanadiel
Community All-Star
Community All-Star

Version 155.0.8059.84 (Official Build) (x86_64) is an outdated version of Chrome.

I suggest first updating Chrome to the latest version, which is Version 158.0.8127.37 (Official Build) (64-bit)

Please See here how to update Chrome if you are not sure how to update it.

 

I tested this on Chrome version 58.0.8127.37 (Official Build) (64-bit) and unless I am looking at the wrong box, it is working fine in Chrome.

I circled the box I think we are talking about in red:

Untitled.jpg

The availability check itself also works under Chrome, as I also tested that to make sure it does not throw an error.

 

If that is the box we are talking about, then I can only conclude the issue not to be with Chrome itself, or Chromium in general as it also works under Brave which is based on Chromium.

Brave is up to date

Brave 1.100.58 (Official Build) (64-bit)

Chromium: 158.0.8127.42
 
It is also not an issue with the load-order problem in the page code because otherwise it would not work for me either under Chrome since I am loading the same code.
 
The possibilities for the error you are experiencing are likely either one or more of the following:
 
- Outdated Chrome version
- One or more Chrome plug-ins interfering with Java script execution
- Corrupted Chrome cache
- In some rare cases issues with Cookies
- In some rare cases firewall or other security settings disabling certain Java scripts
 
I would suggest to try an incognito window and visiting the page using that window. This will automatically disable all plugins and disable any existing cache use, cookie use or any other existing Chrome data.
 
Please See here on how to open and use an incognito window under Chrome.
 
 
I am a Community All-Star and customer. I'm here to help by sharing my knowledge and experience. My views on Bell and the Community Forum are my own and not the views of Bell or any of its affiliates.