Kukhonjiswa imibuzo ethegiwe: Veza yonke imibuzo
  • Kusonjululiwe
  • Okugcinwe kunqolobane

New CSS styles not picked in Firefox.

I am building a website and, for the last couple of days, when I make changes to the CSS file they are no longer being picked up by the browser by which I mean they aren'… (funda kabanzi)

I am building a website and, for the last couple of days, when I make changes to the CSS file they are no longer being picked up by the browser by which I mean they aren't displayed in the web page nor in the developer tools inspector.

They are visible in Chromium browser and dev tools.

I have cleared the cache and refreshed the page to no avail. It is only when I restart the browser that the new style rules take effect in the browser and show up in the dev tools.

Asked by mt3ch 1 unyaka odlule

Answered by cor-el 1 unyaka odlule

  • Kusonjululiwe
  • Okugcinwe kunqolobane

Firefox 76.0 javascript window.open() parameters ignored, tool bar, etc. missing

Until several weeks ago, new windows created through Javascript with window.open() worked. We could pass the new size, and other features, e.g. menubar, toolbar, etc. and… (funda kabanzi)

Until several weeks ago, new windows created through Javascript with window.open() worked. We could pass the new size, and other features, e.g. menubar, toolbar, etc. and they would show up. As of v.76.0 this is no longer true. The parameters are ignored. If we use no parameters, the menubar, etc. do show, but we can't control any new window features. We have not changed our programs at all, and window.open() parameters still work correctly in Chrome, Brave, Edge, etc. How do we get Firefox to recognize the window.open() parameters (again)?

Asked by jjacobs3 2 iminyaka edlule

Answered by jscher2000 - Support Volunteer 2 iminyaka edlule

  • Kusonjululiwe
  • Okugcinwe kunqolobane

Content-Security-Policy: frame-ancestors doesn't work

As mentioned here https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy/frame-ancestors, CSP: frame-ancestors is supported from Firefox 33. Ho… (funda kabanzi)

As mentioned here https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy/frame-ancestors, CSP: frame-ancestors is supported from Firefox 33. However, it seems doesn't work.

I am trying to embed a 3-party site into our page using an iframe. The 3-party site did whitelist us using these headers - Content-Security-Policy: frame-ancestors 'self' https://*.ourdomain.com - X-Frame-Options: SAMEORIGIN

It works fine on Chrome, but not Firefox. I am using Firefox 79.

Is there anything wrong with our headers?

Thank you!

Asked by vinh.vu 1 unyaka odlule

Answered by vinh.vu 1 unyaka odlule

  • Kusonjululiwe
  • Okugcinwe kunqolobane

Notifications Not Working

Hello. I'm using a brand-new installation of Firefox 78.0.1 on a freshly installed copy of Windows 10 Pro. The only way I can get Firefox to display any notifications i… (funda kabanzi)

Hello. I'm using a brand-new installation of Firefox 78.0.1 on a freshly installed copy of Windows 10 Pro. The only way I can get Firefox to display any notifications is by having alerts.useSystemBackend set to true. While this is set to false, notifications will not work. If I use this site to test them, it just says, 'queued for display', followed immediately by 'closed'. I've also tried creating a new profile and testing it again with no success. All sites were granted notification permissions in each case.

Thanks for any help.

Asked by dojima 1 unyaka odlule

Answered by dojima 1 unyaka odlule

  • Okugcinwe kunqolobane

TypeError: document.getelementbyid(...) is null

Although there is a proper id on html but still its showing "TypeError: document.getelementbyid(...) is null". <!DOCTYPE html> <html lang="en"> <head>… (funda kabanzi)

Although there is a proper id on html but still its showing "TypeError: document.getelementbyid(...) is null".


<!DOCTYPE html>
<html lang="en">
<head>
    <meta charset="UTF-8">
    <meta name="viewport" content="width=device-width, initial-scale=1.0">
    <meta http-equiv="X-UA-Compatible" content="ie=edge">
    <title>Fundraising made simple</title>
</head>
<body>
              <form method="post" action="" >
                  <button class="btn btn-success" style="margin: 14px;margin-left: 3em;" name="input_amount" id="total_ammount" value="00.00" type="submit" >Pay </button>
              </form>
<script>
function myFunction(id) {
    console.log('hello all',id)
    document.getElementById('ammounth1').innerHTML = '$ '.concat(counts.toFixed(2));
    document.getElementById('ammounth2').innerHTML = '$ '.concat(count_percentage.toFixed(2));
    document.getElementById('ammounth3').innerHTML = "Paypal will be billed : $ ".concat( total)
    document.getElementById('total_ammount').setAttribute('value',total)
}
</script>


    </div>
<!-- test to see if user is logged in our not -->
<!-- True -->

<!-- Google site tag code -->
    
        
    

<!-- fullscreen fg fields background -->
    
    <style>
        body {
        background: url("https://alphabetacharlie.s3-eu-west-1.amazonaws.com/media/images/KICKSTARTER_FUNDGRAZING_WALLET.png") no-repeat center center fixed;
        -webkit-background-size: cover;
        -moz-background-size: cover;
        -o-background-size: cover;
        background-size: cover;
        }
    </style>
    

    <footer>
        <div class="container">
            <h5> &copy; Copyright 2020 fundgrazing.com All Rights Reserved <a href="/accounts/contact_us/" target="_blank">Contact Us</a>  |  <a href="/accounts/gdpr/" target="_blank">GDPR</a></h5>
        </div>
    </footer>

<!-- Twitter universal website tag code -->
<script>
    !function(e,t,n,s,u,a){e.twq||(s=e.twq=function(){s.exe?s.exe.apply(s,arguments):s.queue.push(arguments);
    },s.version='1.1',s.queue=[],u=t.createElement(n),u.async=!0,u.src='//static.ads-twitter.com/uwt.js',
    a=t.getElementsByTagName(n)[0],a.parentNode.insertBefore(u,a))}(window,document,'script');
    // Insert Twitter Pixel ID and Standard Event data below
    twq('init','o3hea');
    twq('track','PageView');
    </script>
    <!-- End Twitter universal website tag code -->

</body>
</html>

Asked by dvskhamele 1 unyaka odlule

Last reply by jscher2000 - Support Volunteer 1 unyaka odlule

  • Okugcinwe kunqolobane

How can I use the network monitor with a HTTP/2 connection?

I found multiple pages recently that cause problems with the network monitor in firefox developer tools. I attached an image as an example. The three requests are selecte… (funda kabanzi)

I found multiple pages recently that cause problems with the network monitor in firefox developer tools. I attached an image as an example. The three requests are selected always as a "block". They seem to be somehow related but I do not find any documentation what their relation is. My educated guess (also see https://superuser.com/questions/1537396/what-is-the-reason-firefox-combines-multiple-requests-in-the-network-monitor) that it is HTTP/2 related. However I still do not get how to handle debugging in such circumstances. I'd like to see the individual requests and answers for debugging purposes. I do not find a way to reach that goal. Is it a technical restriction?

Asked by ChristianLupus 2 iminyaka edlule

Last reply by TyDraniu 1 unyaka odlule

  • Okugcinwe kunqolobane

Lax Cookie Not Sent in iFrame on 302 Redirection

I’m building an Angular application that is using OAuth2 Auth Code w/PKCE. The app uses hidden iframes to silently renew access tokens. I found that when the OAuth2 autho… (funda kabanzi)

I’m building an Angular application that is using OAuth2 Auth Code w/PKCE. The app uses hidden iframes to silently renew access tokens. I found that when the OAuth2 authorization serve redirects the iFrame to {parent origin}/silent-refresh.html with a 302, Firefox does not send any cookies set with SameSite: Lax.

SameSite: None cookies are sent as expected.

I compared this with IE and Chrome and both of those browser send the Lax cookies on when redirecting due to a 302.

This problem seems to only occur when the iFrame is being redirected via 302 from a different origin. I.e requests from a basic iFrame to the parent page origin send Lax cookies with no problem.

Anyone experience this? Is this expected behavior for Firefox?

Firefox Version 68.8

Asked by brian.l.coker 2 iminyaka edlule

Last reply by brian.l.coker 2 iminyaka edlule