Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

inlined some CSS#19997

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Merged
fabpot merged 1 commit intosymfony:masterfromfabpot:exception-css-inlining
Sep 21, 2016
Merged

Conversation

@fabpot
Copy link
Member

QA
Branch?master
Bug fix?no
New feature?no
BC breaks?no
Deprecations?no
Tests pass?yes
Fixed ticketsn/a
LicenseMIT
Doc PRn/a

This PR has several goals:

  • It fixes the discrepancy between where CSS files were stored (FrameworkBundle) and where there were used (TwigBundle);
  • It removes the need to install the assets to get exceptions (think Silex, micro-kernel-based-edition, ...);
  • It makes things consistent with how we already manage images for exceptions (they are inlined);
  • It makes things consistent with how we manage assets for the web profiler.

@fabpot
Copy link
MemberAuthor

If you are wondering why we did not cleanup this before, that's because those CSSes were shared between the web profiler and the twig exception files, but that's not the case anymore since the redesign of the web profiler.

<linkhref="{{ absolute_url(asset('bundles/framework/css/exception.css')) }}"rel="stylesheet"type="text/css"media="all" />
<style>
.sf-reset.traces {
padding-bottom:14px;
Copy link
Contributor

Choose a reason for hiding this comment

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

is it better use separate css file and include it here?

robfrawley reacted with thumbs down emoji
Copy link
MemberAuthor

Choose a reason for hiding this comment

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

What would be the benefit? It means adding a controller to handle it.

robfrawley reacted with thumbs up emoji
Copy link
Contributor

Choose a reason for hiding this comment

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

Copy link
MemberAuthor

Choose a reason for hiding this comment

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

I agree, this is indeed what is done elsewhere, but here, I don't want to "pollute" the namespace as there are only exceptions templates, and creating a new directory up sounds like not really useful.

@nicolas-grekas
Copy link
Member

👍

@fabpot
Copy link
MemberAuthor

added the change to the CHANGELOG file

@fabpotfabpot merged commitf354638 intosymfony:masterSep 21, 2016
fabpot added a commit that referenced this pull requestSep 21, 2016
This PR was merged into the 3.2-dev branch.Discussion----------inlined some CSS| Q             | A| ------------- | ---| Branch?       | master| Bug fix?      | no| New feature?  | no| BC breaks?    | no| Deprecations? | no| Tests pass?   | yes| Fixed tickets | n/a| License       | MIT| Doc PR        | n/aThis PR has several goals:* It fixes the discrepancy between where CSS files were stored (FrameworkBundle) and where there were used (TwigBundle);* It removes the need to install the assets to get exceptions (think Silex, micro-kernel-based-edition, ...);* It makes things consistent with how we already manage images for exceptions (they are inlined);* It makes things consistent with how we manage assets for the web profiler.Commits-------f354638 inlined some CSS
@fabpotfabpot deleted the exception-css-inlining branchSeptember 21, 2016 21:18
@fabpotfabpot mentioned this pull requestOct 27, 2016
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

1 more reviewer

@KocKocKoc left review comments

Reviewers whose approvals may not affect merge requirements

Assignees

No one assigned

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@fabpot@nicolas-grekas@Koc@carsonbot

[8]ページ先頭

©2009-2025 Movatter.jp