Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 9 months ago

Centering QR code component with -ms-transform

P
Tomislav Šuto•260
@RetroApe
A solution to the QR code component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What are you most proud of, and what would you do differently next time?

I am just proud I managed to match the design :)

What challenges did you encounter, and how did you overcome them?

There were some little challenges like working with Git, nothing to write home about.

What specific areas of your project would you like help with?

Although the project was simple to do, centering an element vertically and horizontally seems to be more complicated than it should. Using flex is possible (I think), but I decided to use positioning:

.container {
    position: absolute;
    top: 50%;
    left: 50%;
    -ms-transform: translate(-50%, -50%);
    transform: translate(-50%, -50%);
}

I understand the transform property, but I don't understand what is -ms-transform property supposed to be and what does it do. If anyone has an answer or has a link with a good explanation, I am happy to devour it :)

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    lai yiu leung•400
    @jasper2virtual
    Posted 9 months ago

    Although translate and absolute positioning can get the job done, but this is the technique decades ago. In modern css, flex and grid are the better tools when you try to build the structure of layout.

    Positioning and translation is still useful today, depending on the use case. One example is building the dynamic widget on screen.

    Marked as helpful
  • Esteban•670
    @evertzner
    Posted 9 months ago

    Hi, nice job!

    The -ms- is a vendor prefix, this allows developers to change browser configurations to test upcoming features. Browsers now add experimental features behind user-controlled flags or preferences. Flags can be added for smaller specifications enabling reaching a stable state much more quickly.

    Those prefixes are:

    • -webkit- (Chrome, Safari, newer versions of Opera and Edge, almost all iOS browsers including Firefox for iOS; basically, any WebKit or Chromium-based browser)
    • -moz- (Firefox)
    • -o- (old pre-WebKit versions of Opera)
    • -ms- (Internet Explorer and Microsoft Edge, before Chromium)

    In my opinion, you should try to strengthen your flex and grid skills. It will let you do incredible things!

    Marked as helpful

Join our Discord community

Join thousands of Frontend Mentor community members taking the challenges, sharing resources, helping each other, and chatting about all things front-end!

Join our Discord

Stay up to datewith new challenges, featured solutions, selected articles, and our latest news

Frontend Mentor

  • Unlock Pro
  • Contact us
  • FAQs
  • Become a partner

Explore

  • Learning paths
  • Challenges
  • Solutions
  • Articles

Community

  • Discord
  • Guidelines

For companies

  • Hire developers
  • Train developers
© Frontend Mentor 2019 - 2025
  • Terms
  • Cookie Policy
  • Privacy Policy
  • License

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

How does the accessibility report work?

When a solution is submitted, we use axe-core to run an automated audit of your code.

This picks out common accessibility issues like not using semantic HTML and not having proper heading hierarchies, among others.

This automated audit is fairly surface level, so we encourage to you review the project and code in more detail with accessibility best practices in mind.

How does the CSS report work?

When a solution is submitted, we use stylelint to run an automated check on the CSS code.

We've added some of our own linting rules based on recommended best practices. These rules are prefixed with frontend-mentor/ which you'll see at the top of each issue in the report.

The report will audit all CSS, SCSS and Less files in your repository.

How does the HTML validation report work?

When a solution is submitted, we use html-validate to run an automated check on the HTML code.

The report picks out common HTML issues such as not using headings within section elements and incorrect nesting of elements, among others.

Note that the report can pick up “invalid” attributes, which some frameworks automatically add to the HTML. These attributes are crucial for how the frameworks function, although they’re technically not valid HTML. As such, some projects can show up with many HTML validation errors, which are benign and are a necessary part of the framework.

How does the JavaScript validation report work?

When a solution is submitted, we use eslint to run an automated check on the JavaScript code.

The report picks out common JavaScript issues such as not using semicolons and using var instead of let or const, among others.

The report will audit all JS and JSX files in your repository. We currently do not support Typescript or other frontend frameworks.

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub