Skip to content

Conversation

@connorjclark
Copy link
Collaborator

would have prevented #12936

@connorjclark connorjclark requested a review from a team as a code owner September 2, 2021 21:25
@connorjclark connorjclark requested review from patrickhulce and removed request for a team September 2, 2021 21:25
@google-cla google-cla bot added the cla: yes label Sep 2, 2021
async function getRobotsTxtContent() {
try {
const response = await fetch(new URL('/robots.txt', location.href).href);
const response = await fetch(new window.__nativeURL('/robots.txt', location.href).href);
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

took awhile to figure out why the smoke test wasn't passing, it's because seo tester html overrides URL! so, luckily we get a driveby fix here for naughty pages overriding globals.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

hm, _cachedNativesPreamble should be solving this, is something broken there? that's more concerning than the smoke itself :/

/**
* Prefix every script evaluation with a shadowing of common globals that tend to be ponyfilled
* incorrectly by many sites. This allows functions to still refer to `Promise` instead of
* Lighthouse-specific backups like `__nativePromise` (injected by `cacheNativesOnNewDocument` above).
*/
static _cachedNativesPreamble = [
'const Promise = globalThis.__nativePromise || globalThis.Promise',
'const URL = globalThis.__nativeURL || globalThis.URL',
'const performance = globalThis.__nativePerformance || globalThis.performance',
].join(';\n');

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ok so this seems fine and i can't get it to fail again, weird

@connorjclark connorjclark changed the title test(smoke): check for passing robots-txt tests(smoke): check for passing robots-txt Sep 2, 2021
@connorjclark
Copy link
Collaborator Author

connorjclark commented Sep 3, 2021

@patrickhulce / @adamraine any idea why FR is failing seo-passing / to fetch robots.txt?

@adamraine
Copy link
Contributor

Could it be flaky? I'm not seeing a failure locally on the smoke test or a direct FR navigation of the test page.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants