Page MenuHomePhabricator

Create desktop.css/js for specific non-mobile styles and scripts
Closed, DuplicatePublic

Description

Сейчас по умолчанию при наличии мобильного скина, он не использует Common.css/js
Из-за этого все универсальные стили и скрипты приходится дублировать, что неудобно. Вики имеющие гаджеты решают эту проблему с помощью гаджетов, но это решение — это костыль для хромого. Есть отдельные страницы под каждый скин, но требуются также отдельные страницы под тип устройства (desktop/mobile), и общие абсолютно для всех без исключения.
—————
In this moment by default, if you have a mobile skin, it does not use the Common.css/js
This versatile styles and scripts have to duplicate that uncomfortable. Wiki with gadgets solve this problem with the help of gadgets, but this decision is a crutch for the lame. There is a separate pages for each skin, but also requires a separate pages for the device type (desktop/mobile) and separate for commons without exception.

Skin inheritance scheme.jpg (320×640 px, 39 KB)

Event Timeline

Aklapper renamed this task from Create desktop.css/js for specific non-mobile styles and scrypts to Create desktop.css/js for specific non-mobile styles and scripts.Feb 6 2021, 10:03 PM

We are trying to move away from the concept of desktop vs mobile styles since users use desktop to view mobile and mobile users use desktop and to think in terms of skin e.g. Minerva.css or Vector.css (particularly because Minerva works for both mobile and desktop).

Longer-term, we plan to remove Mobile.js/css from MobileFrontend and load Common.js/css. We recommend using TemplateStyles making use of media queries to ship styles rather than shipping desktop and mobile stylesheets.

We are trying to move away from the concept of desktop vs mobile styles

Does that mean this task should have status declined?

We are trying to move away from the concept of desktop vs mobile styles since users use desktop to view mobile and mobile users use desktop and to think in terms of skin e.g. Minerva.css or Vector.css (particularly because Minerva works for both mobile and desktop).

Longer-term, we plan to remove Mobile.js/css from MobileFrontend and load Common.js/css. We recommend using TemplateStyles making use of media queries to ship styles rather than shipping desktop and mobile stylesheets.

Oh thanks for the advice with the extension, I'll try. But my request does not duplicate yours and it seems more realistic and simpler.