Add device-specific responsive visibility controls for blocks/patterns

Ouverte
#198 1 commentaire 0 réactions 0 personnes assignées Voir sur GitHub

Personne n'a encore pris cette issue.

Évaluation

Difficulté
5/5
Temps estimé
Plus d'une semaine
Accessibilité débutants
15/100
Type d'issue
Fonctionnalité
Clarté
À clarifier
Activité
Active
Stack technique
css, php
Domaine
frontend

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

feature-request-triage

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: none via 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

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de Codeinwp/raft

Toutes les issues de Codeinwp/raft

Issues similaires

Plus d'issues PHP

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.