Add device-specific responsive visibility controls for blocks/patterns
Personne n'a encore pris cette issue.
Évaluation
- Difficulté
- 5/5
- Temps estimé
- Plus d'une semaine
- Accessibilité débutants
- 15/100
Piste de recherche
The payload names no files, tests or entry points, so the first step is finding where Raft defines its container and group blocks. The repository description says issues should be filed in Codeinwp/otter-blocks, so confirm with maintainers which project owns this before writing code. Done means a Desktop/Tablet/Mobile visibility toggle in the inspector that applies display: none through media queries in both the editor preview and the frontend.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Description
Impact: 65 · Confidence: 90 · Complexity: 55
Description
Problem
Users cannot display different banner blocks or content patterns depending on screen size (e.g. desktop vs. mobile). Standard Gutenberg blocks in Raft render across all screen sizes without native options to hide or show specific sections on mobile or desktop.
Desired Behavior
Provide responsive visibility settings on theme container/group blocks or block patterns allowing site creators to toggle visibility per device breakpoint (Desktop, Tablet, Mobile).
Acceptance Criteria
- Include a 'Responsive / Visibility' panel in the block inspector for standard theme block containers.
- Allow users to toggle visibility settings independently for Desktop, Tablet, and Mobile screens.
- Ensure hidden blocks apply appropriate CSS rules (e.g.,
display: nonevia media queries) on target screen sizes in both editor preview and frontend.
Customer Context
Feedback entry 1 (active for 74 days, deactivated due to missing options): Customer needed to customize mobile view by serving specific banner variations per screen size, but found no built-in theme options to achieve responsive banner visibility.
Root Cause Analysis
The customer wants to present distinct banner layouts optimized separately for mobile and desktop screens. Standard Gutenberg FSE theme structures in Raft lack built-in responsive visibility toggles (hide on mobile / hide on desktop) for core block containers or patterns, requiring external plugins or custom CSS to achieve device-specific block rendering.
Reasoning
The user uninstalled Raft because they were unable to set up different banners for different screen sizes (specifically desktop vs mobile view). Raft is a standard FSE block theme relying on default Gutenberg block controls, which natively lack per-device display rules or responsive block visibility controls for hero banners. While block plugins like Otter provide section visibility conditions, Raft itself lacks native responsive display controls or device-specific block variation settings.
Source: automated uninstall feedback — raft, 2026-11-02
Generated by feature-request-triage workflow (ID: feature-request-triage_6ae96a93e3f317.68702671)
- Langage dominant
- PHP
- Étoiles
- 8
- Forks
- 4
- Merge moyen
- 7 h 18 min
- PR mergées (30 j)
- 6
Préparer son environnement
- Aucun Dockerfile ni fichier Docker Compose
- Propose un modèle de pull request
- Aucun guide de contribution
Par où commencer
- Lisez l'issue en entier, puis le guide de contribution du projet.
- Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
- Forkez le dépôt et travaillez sur une branche.
- Ouvrez une pull request qui référence le numéro de l'issue.
Autres issues de Codeinwp/raft
-
Difficulté 2/5 1-3 heures Accessibilité débutants 77/100
-
Mobile Menu Raft 1.1.5Ouverte
Difficulté 3/5 1-2 jours Accessibilité débutants 25/100
-
bug
Difficulté 3/5 1-2 jours Accessibilité débutants 35/100
-
Custom palette colors don't workOuvertebug customer report
Difficulté 3/5 1-2 jours Accessibilité débutants 35/100
-
Font sizes at Frontend vs EditorOuverte
Difficulté 3/5 1-2 jours Accessibilité débutants 35/100
Toutes les issues de Codeinwp/raft
Issues similaires
-
Change: check an identifier filter the same way in every tool - the order of somcp_search_ordersOuverteconsistency enhancement Orders
Difficulté 1/5 Moins d'une heure Accessibilité débutants 88/100
novalo-dev/Prestashop-MCP-Server#343 ·
Les mainteneurs répondent en général sous 1 jour
-
Difficulté 2/5 1-3 heures Accessibilité débutants 72/100
Les mainteneurs répondent en général sous 1 jour
-
claude
Difficulté 2/5 1-3 heures Accessibilité débutants 72/100
sprain/sprainocchio#45 ·
Les mainteneurs répondent en général sous 1 jour
-
sync-en
Difficulté 1/5 Moins d'une heure Accessibilité débutants 85/100
Les mainteneurs répondent en général sous 1 jour
-
sync-en
Difficulté 1/5 Moins d'une heure Accessibilité débutants 85/100
Les mainteneurs répondent en général sous 1 jour