* Update base template style for header, body and footer based on new designs
Update header for base template, move search input from header in main content instead and update search style
Update header navigation links/buttons and add new icons
Add padding to prevent content jumping
Merge update footer for desktop only to look like mozilla.org footer to resolve conflicts. (#3230)
* change footer background color to black
* Applied updates to footer to match footer on mozilla.org
* Update Mozilla and Firefox list headers and add language picker to footer
* Remove mozilla.org at the end of the contribution link
* Fix Donate utm_source param and contribute to site link
Update footer links font-weight to bold
* Fix header paddings
* Add new optimized mozilla support SVG to use in header instead of PNG
* Add underline text-decoration to header links
* Add missing fonts
* Change default font-family to Open Sans and use Zilla Slab for special cases.
* Add hover feedback on buttons.
* Fix nav list and buttons display when on smaller screens.
* Fix nav list display when on smaller screens and signed in.
* Make adjustments to header links wrapping.
* Fix formatting and padding issue
* Change #aux-nav-left to #aux-nav to not break other functionality using #aux-nav reference
* Make adjustments to header.
* Fix issue with header search input when search results are shown.
* Make main search take up full width like mockup.
* Chain focus and val calls.
This commit includes:
- Backend ignore request to mark ready to localize if the revision is
of TYPO_SIGNIFICANCE.
- Reworked tests so that if they want an localization mail, it needs to
be able to use MEDIUM_SIGNIFICANCE.
- Hide the option for mark as ready for localization if reviewer
selects typo significance in the front end.
Depends on:
- PR #1395
Style fix
Fixed up the code. Added tests
Two things happened here:
* The view was not extending data to the present day. On most archived
articles, that means that the default viewing window for k.Graph shows
no data, which makes it angry. This commit makes the view add zeroes
to the data to fill it in.
* k.Graph couldn't deal with series of all zeroes, or other strange data
sets. This commit added some checks for good graph scales.
* Series used to calculate minimums as well as maximums. This wasn't
used, so I axed it.
This uses "axis groups". Each axis group's maximum is calculated, and
then the entire group is scaled so that the maximum is 1.0. Then the
axises and the hover tool tips are adjusted to show the correct numbers.
The scaling is adjusted as the zoom is changed and as acises are toggled
on and off.
This is kind of hacky, and the more I do this, the more I want to just
use d3 directly.
This means that instead of an array of x/y pairs for each line on the
graph (which duplicates data like the created times), there is an array
of objects which represent a moment in time, and all the values at that
time.
This assumes that each point in time will have a value for all of the
data points, or at least most of them. Rickshaw does not make this
assumption, but k.Graph now does, mainly because it has held true in all
the data we have used so far.
This makes progress towards completing bug 865378.
Matthew Lagace
Shuhao Wu
Ricky Rosario
Mike Cooper
Rehan Dalal
Michał Frontczak
Joshua Smith