Skip to content
This repository has been archived by the owner on Mar 15, 2018. It is now read-only.

Do not force portrait orientation (bug 844186) #2336

Merged
merged 1 commit into from Jul 22, 2014
Merged

Do not force portrait orientation (bug 844186) #2336

merged 1 commit into from Jul 22, 2014

Conversation

dethe
Copy link
Contributor

@dethe dethe commented Jul 22, 2014

The zamboni part of unlocking portrait orientation (so orientation can match device).

@diox
Copy link
Member

diox commented Jul 22, 2014

Not quite sure why we have a django view serving our manifest when we could simply serve the fireplace file, but r+

@dethe
Copy link
Contributor Author

dethe commented Jul 22, 2014

I have no idea. I'll try to test to see if we actually use it.

dethe added a commit that referenced this pull request Jul 22, 2014
Do not force portrait orientation (bug 844186)
@dethe dethe merged commit e7e6057 into mozilla:master Jul 22, 2014
@dethe dethe deleted the unlock_portrait branch July 22, 2014 17:29
@cvan
Copy link
Contributor

cvan commented Jul 23, 2014

because Fireplace is still served from Zamboni. and it's useful for generating etags, etc. I filed a bug about using Fireplace to serve content.

@diox
Copy link
Member

diox commented Jul 23, 2014

In the meantime, maybe it would be nice to have zamboni parse & serve what fireplace provides, to keep things DRY...

@cvan
Copy link
Contributor

cvan commented Jul 23, 2014

In the meantime, maybe it would be nice to have zamboni parse & serve what fireplace provides, to keep things DRY...

that could be slow, and there's some server-side logic right now

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
3 participants