Add device-specific responsive visibility controls for blocks/patterns
まだ誰も着手していません。
評価
調査の方向性
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.
索引モデルが issue の本文から書いたものです。
説明
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)
- 主要言語
- PHP
- スター
- 8
- フォーク
- 4
- 平均マージ
- 7時間 18分
- マージ済み PR(30日)
- 6
環境構築
- Dockerfile・Docker Compose ファイルなし
- プルリクエストのテンプレートあり
- コントリビューションガイドなし
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
Codeinwp/raft のほかの issue
-
難易度 2/5 1〜3時間 初心者へのやさしさ 77/100
-
難易度 3/5 1〜2日 初心者へのやさしさ 25/100
-
bug
難易度 3/5 1〜2日 初心者へのやさしさ 35/100
-
bug customer report
難易度 3/5 1〜2日 初心者へのやさしさ 35/100
-
難易度 3/5 1〜2日 初心者へのやさしさ 35/100
似ている issue
-
Change: check an identifier filter the same way in every tool - the order of somcp_search_ordersオープンconsistency enhancement Orders
難易度 1/5 1時間未満 初心者へのやさしさ 88/100
novalo-dev/Prestashop-MCP-Server#343 ·
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 72/100
メンテナーはふだん 1 日以内に返信
-
claude
難易度 2/5 1〜3時間 初心者へのやさしさ 72/100
sprain/sprainocchio#45 ·
メンテナーはふだん 1 日以内に返信
-
sync-en
難易度 1/5 1時間未満 初心者へのやさしさ 85/100
メンテナーはふだん 1 日以内に返信
-
sync-en
難易度 1/5 1時間未満 初心者へのやさしさ 85/100
メンテナーはふだん 1 日以内に返信