BlackFriday 2024! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Adobe Exam AD0-E706 Topic 1 Question 30 Discussion

Actual exam question for Adobe's AD0-E706 exam
Question #: 30
Topic #: 1
[All AD0-E706 Questions]

You added a grunt autoprefixer command, which adds CSS vendor prefix like --webkit- and --moz- to CSS files generated by the setup:static-connect: deploy command.

After deployment you still see CSS files without prefixes. The hooks section in the .magento. app. Yaml file is:

Considering static assets are being generated on the build phase why are CSS prefixes missing?

Show Suggested Answer Hide Answer
Suggested Answer: C

Contribute your Thoughts:

Santos
5 months ago
That makes sense too. So it could be a combination of both timing and where the prefixes are added
upvoted 0 times
...
Honey
6 months ago
I believe CSS vendor prefixes must be added to CSS files locally and committed as part of a theme
upvoted 0 times
...
Katie
6 months ago
That's a good point, it's possible. Maybe we should check the order of commands in the deployment process
upvoted 0 times
...
Santos
6 months ago
But could it also be that the custom command was run before static assets were transferred into the init directory?
upvoted 0 times
...
Katie
6 months ago
I think the issue might be that the static assets were not generated yet when the grunt command ran
upvoted 0 times
...
Alise
7 months ago
That's possible. The command needs to run after static assets are generated.
upvoted 0 times
...
Tyra
7 months ago
So, the problem could be the timing of when the custom command was executed?
upvoted 0 times
...
Lorrie
7 months ago
Could it be because the custom command ran before assets were transferred?
upvoted 0 times
...
Alise
7 months ago
The grunt command may have run before static assets were generated
upvoted 0 times
...
Tyra
7 months ago
Why are CSS prefixes missing after deployment?
upvoted 0 times
...

Save Cancel