Webflow only pastes its own elements; a developer built a way to paste SVG and HTML

·4 views

Webflow's Designer accepts only its own elements on paste, so copying an icon from Figma or plain HTML and CSS into it does nothing. The usual workaround, a Code Embed, works but is a black box whose contents cannot be selected, classed, or styled in the Style panel. The developer behind devpack built SVG to Webflow and HTML & CSS to Webflow tools, plus a browser extension that performs the conversion directly when pasting into the Designer. The approach works by inspecting the JSON Webflow places on the clipboard, which uses a flat list of nodes and a separate styles list, and then writing equivalent JSON that the Designer will paste. Because the modern Clipboard API cannot write that custom type, the developer relies on the older copy-event method, which remains the only viable option despite being deprecated.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Google overhauls YouTube's immersive view on Meta Quest and VR glasses

Google is reportedly redesigning the YouTube app's immersive viewing mode on Meta Quest and other VR glasses, aligning it more closely with Android XR and visionOS experiences. The shift suggests that watching video in headsets is moving from an occasional feature toward a routine habit. The article argues this matters beyond convenience, since sustained daily use makes it practical to layer vision-training activities onto existing viewing habits. It highlights Amblyotube, a Meta Quest app that sends different visual feeds to each eye during streamed content to support amblyopia (lazy eye) therapy. The app positions itself as an educational aid rather than a diagnostic or curative treatment, and is limited to users aged 13 and older.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Government agencies issue vendor questionnaire on post-quantum cryptography readiness

On November 4, the NSA, CISA, and Australia's ASD's ACSC published a 19-page guide of questions for buyers to ask software and hardware vendors about their post-quantum cryptography readiness. The document is a joint update of an earlier Australian version released in July. It follows NIST's final transition plan, which deprecates RSA and elliptic-curve cryptography after 2030 and disallows them after 2035. The guidance centers on a cryptographic bill of materials that inventories every algorithm, library, and configuration a product relies on, including those inherited from third parties. Buyers are encouraged to ask whether vendors can provide such an inventory and when post-quantum-ready releases will ship in time for deployment before 2030.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Proposal Urges Experience Decision Records to Align UX and Developers

The author proposes adopting Experience Decision Records, modeled on Architectural Decision Records, to capture both UX decisions and the reasons behind them. Without this, developers often lack context and either repeatedly ask the UX team for small rules or make inconsistent assumptions. Machine-readable records could also help AI-assisted coding and review tools check compliance with UX guidelines. The author acknowledges setup costs but suggests AI tools could extract existing decisions from emails, chats, and meeting notes to reduce effort. Human review would still be required, and the author argues the records would distribute knowledge more evenly and improve long-term consistency.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Model Context Protocol Explained: How AI Assistants Connect to Everyday Tools

A DEV Community piece walks through how AI assistants can move beyond understanding requests to actually acting on them. It uses the example of checking a calendar and creating a task, noting that language models alone cannot access external applications without integration. The article contrasts understanding an action with executing one, comparing it to frontend and backend separation in software design. It introduces Model Context Protocol (MCP), an open standard that gives AI applications a common way to connect to external tools, systems, and data sources, much as USB standardizes device connections. The author stresses that MCP does not replace the underlying APIs, which services still need to communicate with their own systems.

0 comments Read more at DEV Community