awesome-web | A curated list of awesome resources for web developers | Awesome List library

Delete the VOLUME line.

The only particularly obvious effect of a VOLUME directive is that it prevents any following RUN command from changing that directory. Declaring a VOLUME in your Dockerfile is almost never necessary (and volumes aren't appropriate storage for source code); you can just delete that line and nothing bad will happen.

If you give width to your social-icons you can align your items to center.

like below;

CSS url() is not processed by Django static files but called directly from Browser

As you are using relative path resolved path value is expected. You will need to have some preprocessing of this CSS file to set the bucket name to URL if you have multiple deployments of it or just set it to absolute bucket path

I ended up going with angular-fontawesome. It was super easy to implement, integrates well and renders rapidly and most importantly there were no issues when on a AWS Serverless Application. Also you only load up the icons you use - no extra baggage. https://github.com/FortAwesome/angular-fontawesome

Also a very handy Stackblitz to test icons... https://stackblitz.com/edit/angular-fontawesome-sample?file=src%2Fapp%2Fapp.module.ts

create a list that will store links

That's SCSS. You need to put compiled CSS there. You may also see SASS which is like a cousin of the SCSS language where instead of {} you use the tab indent syntax. Nevertheless your browser cannot understand SASS/SCSS.

Secondly, you seem to have not linked your javascript/jquery and css file in the head tag or anywhere.

Link CSS Link Jquery/JS

Replacing sandbox with sandbox allow-same-origin in the CSP policy will fix the problem.

Explanation:

The CORS problem the question describes is ultimately caused by the fact the browser is setting the origin value to null. So even though the Access-Control-Allow-Origin response header is set to the origin value that’d normally be expected — matching the URL shown in the browser address bar — it actually doesn’t match, due to the fact the browser has set the origin to null.

So you end up in what looks like a paradox, with the document seeming to not match its own origin.

The answer at https://stackoverflow.com/a/42242802/441757 outlines all cases where browsers set an origin to null. The specific cause of the case in the question arises from HTML spec text at https://html.spec.whatwg.org/multipage/#attr-iframe-sandbox which states that if sandbox is set:

…the content is treated as being from a unique origin, forms, scripts, and various potentially annoying APIs are disabled, links are prevented from targeting other browsing contexts, and plugins are secured. The allow-same-origin keyword causes the content to be treated as being from its real origin instead of forcing it into a unique origin.

So the bottom line is: Whenever you specify sandbox somewhere, in most cases you want to be specifying it with the allow-same-origin keyword included — in order to prevent surprising and hard-to-troubleshoot problems/side-effects such as the CORS problem described in the question.

There are several ways to accomplish this depending on your preference. The biggest issue you're facing, is that you assume the dropdown-content should know the width of it's parent. An absolute positioned element can only know the width of it's parent under certain conditions - and those conditions aren't being met.

Option #1. (Simplest) way to make the the drop-down the same width is to set a fixed width to your class (.dropdown-content) that matches the fixed width of your button that activates it.

Option #2. A more (Dynamic) way is to set the parent class (.dropdown) a position:relative. Due to your structure, there are several other changes you'll have to make to get the desired result such as getting rid of the overflow:hidden on .navbar & .dropdown.

Option #3. The (Recommended) way would be changing your structure of the Nav Bar & it's contents completely. The .navbar should be position:absolute or position:fixed (depending on how you want the nav bar to behave.) Then each of the .dropdown buttons can be position:absolute or position:relative. Then, your .dropdown-content can be set to width:100%. (Which is the behavior you're looking for).

The CSS code you pasted is in SASS format, you need to compile it first. It looks like you are also missing some JavaScript code there. Try to see the compiled content in Codepen's page.