1996034 - Placeholders showing a lot on release at first run

Status: RESOLVED FIXED

(Firefox :: New Tab Page, defect)

Description

[Mike Kaply [:mkaply]]

Attachment: Screenshot 2025-10-23 at 10-56-47 New Tab.png

On first run of release Firefox (144), I'm seeing extra placeholders that never go away until I open a new tab.

I see them every time I start Firefox.

I do see an error

Content msg:
Object { name: "ActivityStream:MainToContent", data: {…} }
Dispatch error: TypeError: can't access property "loaded", prevState.spocs.onDemand is undefined
DiscoveryStream resource://newtab/data/content/activity-stream.bundle.js:8155
combination Redux
mergeStateReducer resource://newtab/data/content/activity-stream.bundle.js:17182
dispatch Redux
messageMiddleware resource://newtab/data/content/activity-stream.bundle.js:17195
rehydrationMiddleware resource://newtab/data/content/activity-stream.bundle.js:17215
initStore resource://newtab/data/content/activity-stream.bundle.js:17269

That might be related?

Comment 1

[Mike Kaply [:mkaply]]

I also see a lot of CSP errors against home. Not sure if that's related.

Content-Security-Policy: The page’s settings blocked an event handler (script-src-attr) from being executed because it violates the following directive: “script-src resource: chrome:”. Consider using a hash ('sha256-8QfvwaGA+CLDmLlnT19+TKhQpmNGfhFOhRGFhFAPBMI=') together with 'unsafe-hashes'.
Source: () => this.props.onClose() home
Content-Security-Policy: The page’s settings blocked an event handler (script-src-attr) from being executed because it violates the following directive: “script-src resource: chrome:”. Consider using a hash ('sha256-teymo+fQiPF6cS0me8L2qemN75M4ghQnhDk51cjXvpk=') together with 'unsafe-hashes'.
Source: e => {
    e.preventDefault();
    setSh… home
Content-Security-Policy: The page’s settings blocked an event handler (script-src-attr) from being executed because it violates the following directive: “script-src resource: chrome:”. Consider using a hash ('sha256-W/DBp58Hkh3G5g3GTRC0Tc1qVK/JhGFEQXBNmLt5SJk=') together with 'unsafe-hashes'.
Source: function() {
    [native code]
} 8 home
Content-Security-Policy: The page’s settings blocked an event handler (script-src-attr) from being executed because it violates the following directive: “script-src resource: chrome:”. Consider using a hash ('sha256-G7ms7pUd9Cf4YtuISQjYDzMKQs9t4rqZg/SaiF91whI=') together with 'unsafe-hashes'.
Source: () => {
    const updatedSectionData = {… home
Content-Security-Policy: The page’s settings blocked an event handler (script-src-attr) from being executed because it violates the following directive: “script-src resource: chrome:”. Consider using a hash ('sha256-teymo+fQiPF6cS0me8L2qemN75M4ghQnhDk51cjXvpk=') together with 'unsafe-hashes'.
Source: e => {
    e.preventDefault();
    setSh… home
Content-Security-Policy: The page’s settings blocked an event handler (script-src-attr) from being executed because it violates the following directive: “script-src resource: chrome:”. Consider using a hash ('sha256-W/DBp58Hkh3G5g3GTRC0Tc1qVK/JhGFEQXBNmLt5SJk=') together with 'unsafe-hashes'.
Source: function() {
    [native code]
} 12 home
Content-Security-Policy: The page’s settings blocked an event handler (script-src-attr) from being executed because it violates the following directive: “script-src resource: chrome:”. Consider using a hash ('sha256-G7ms7pUd9Cf4YtuISQjYDzMKQs9t4rqZg/SaiF91whI=') together with 'unsafe-hashes'.
Source: () => {
    const updatedSectionData = {… home
Content-Security-Policy: The page’s settings blocked an event handler (script-src-attr) from being executed because it violates the following directive: “script-src resource: chrome:”. Consider using a hash ('sha256-teymo+fQiPF6cS0me8L2qemN75M4ghQnhDk51cjXvpk=') together with 'unsafe-hashes'.
Source: e => {
    e.preventDefault();
    setSh… home
Content-Security-Policy: The page’s settings blocked an event handler (script-src-attr) from being executed because it violates the following directive: “script-src resource: chrome:”. Consider using a hash ('sha256-W/DBp58Hkh3G5g3GTRC0Tc1qVK/JhGFEQXBNmLt5SJk=') together with 'unsafe-hashes'.
Source: function() {
    [native code]
}

Comment 2

[Scott [:thecount] Downe]

Attachment: Bug 1996034 - Newtab guard against older cached data not having on demand spocs

Comment 3

[Pulsebot]

Pushed by [e-mail]:
https://github.com/mozilla-firefox/firefox/commit/a0b293e34d96
https://hg.mozilla.org/integration/autoland/rev/77673c491a57
Newtab guard against older cached data not having on demand spocs r=home-newtab-reviewers,mconley

Comment 4

[Sandor Molnar[:smolnar]]

https://hg.mozilla.org/mozilla-central/rev/77673c491a57