Skip to content
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue #259 - Embed images in CSS so asset fingerprinting works. #260

Merged
merged 3 commits into from
Jul 7, 2013
Merged

Issue #259 - Embed images in CSS so asset fingerprinting works. #260

merged 3 commits into from
Jul 7, 2013

Conversation

pbougie
Copy link
Contributor

@pbougie pbougie commented Jun 28, 2013

Moves images into base64-encoded CSS to fix problems when using the Rails asset pipeline and asset fingerprinting. Changing an image is almost as easy as it was: instead of changing the image in the filesystem, you simply base64 encode it and paste it into the CSS. Use an encoder such as this one: http://webcodertools.com/imagetobase64converter

@OscarGodson
Copy link
Owner

@gankro what do you think about this?

@Gankra
Copy link
Collaborator

Gankra commented Jun 29, 2013

Base64 embedding in CSS:

  • more portable
  • easy for users to clobber/replace
  • less HTTP reqs
  • well supported as far as I can tell
  • better versionable?

Seems like a good call to me. My only issues are implementation specific.

@pbougie
Copy link
Contributor Author

pbougie commented Jun 29, 2013

Since this is all in an iframe, its not clear to me that you need anything more than .epiceditor-fullscreen-foo as the selectors here.

I never touched any of the selectors. Any refactoring of selectors should probably be done elsewhere.

Semantically, should these not be ?

Agreed. I made the changes.

Not a huge fan of useless whitespace edits, but that's just me.

I mistakenly let those go through. I've reverted the whitespace edits. However, trailing whitespace should be removed project-wide but should be done in another commit.

@OscarGodson
Copy link
Owner

@pbougie thanks. I'll take a look at this tonight or something. Did you check IE9-10?

@pbougie
Copy link
Contributor Author

pbougie commented Jun 29, 2013

Works well in IE9-10. Is there somewhere where you list browser compatibility for EpicEditor?

On 2013-06-29, at 15:09 , Oscar Godson notifications@github.com wrote:

@pbougie thanks. I'll take a look at this tonight or something. Did you check IE9-10?


Reply to this email directly or view it on GitHub.

@OscarGodson
Copy link
Owner

Thanks @gankro! The code all looks good to me too. I'm going to test it locally real quick then merge it if it looks good.

@OscarGodson
Copy link
Owner

IE9:
screen shot 2013-07-06 at 1 11 24 pm

@OscarGodson
Copy link
Owner

Buttons are still buttons and base64 doesnt seem to be working.

@pbougie
Copy link
Contributor Author

pbougie commented Jul 6, 2013

@OscarGodson Works fine here. Looks like the new styles are missing. Did you force reload the CSS?

@OscarGodson
Copy link
Owner

I can try again later. Works fine in IE10 mode tho which means the caching shouldn't be a problem.

@OscarGodson OscarGodson merged commit a29595b into OscarGodson:develop Jul 7, 2013
@OscarGodson
Copy link
Owner

@pbougie Deleted everything (cookies, cache, etc) and finally it worked. Hopefully this isn't an issue when upgrading for people.

Thanks again for the contribution :)

OscarGodson added a commit that referenced this pull request Jul 7, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants