Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Figma removed `window.figma` on view-only pages today

forum.figma.com

Post reply on HN
Print view View original

21–30 of 54 posts

Re: Figma removed `window.figma` on view-only pages today

#21

Post by davedx »

theplatman wrote: post #2

Figma’s dev mode was just a way to take existing functionality and gate it behind a higher price point under the guise of “new functionality”. As a developers i found it simpler to access css from figma via the old inspect vs. having to toggle in and out of dev mode. It is shady to take a commonly used feature and move it behind a higher tier after years of offering to people already giving you money. Just classic VC…

They were hella spammy about devmode too, spamming me with marketing mail about it and denying it was marketing. Shady

Re: Figma removed `window.figma` on view-only pages today

#22

Post by freefaler »

vitalurk wrote: post #20

Penpot is great, free, and doesn't rat** you. Oh and it's made by a kickass collective. That is where I went when I binned Figma.

Let's hope they find a sustainable business model, because the people working there needs salaries and hosting needs paying...

Re: Figma removed `window.figma` on view-only pages today

#23

Post by sdwr »

durkie wrote: post #17

So this is kind of tangentially related here, but is there a "state-of-the-art" or best practices on digging through big JS apps / frameworks / objects? Ultimately this is all code running on my machine, so it feels like it should be accessible in the console somewhere . I've had to do a fair amount of this with a Chrome extension I maintain that hooks in to routing (creating bike / running routes) sites, and fortuna…

I'm working in vue, and get lost at the transition between my code and the framework stuff, when an error "falls through the cracks", and the call stack comes from the framework. What do you do for that, even?

Re: Figma removed `window.figma` on view-only pages today

#26

Post by KaiMagnus »

I didn’t know anything was degraded (I’m not the one doing tooling decisions in my org. There were some emails about dev mode, but nothing that really highlighted any impact/changes) until a developer reached out to me a couple weeks ago and wanted to know the names of a couple of icons, colors, etc.

The changes were a clear step backwards and this change shows some real pettiness. I guess if you’re on top, money is better than goodwill. Seems like they’re turning the monetization to 11 now after investors couldn’t cash out with Adobe. Let’s not forget that it was Adobe that ultimately called it off.

Re: Figma removed `window.figma` on view-only pages today

#27

Post by hnrodey »

durkie wrote: post #17

So this is kind of tangentially related here, but is there a "state-of-the-art" or best practices on digging through big JS apps / frameworks / objects? Ultimately this is all code running on my machine, so it feels like it should be accessible in the console somewhere . I've had to do a fair amount of this with a Chrome extension I maintain that hooks in to routing (creating bike / running routes) sites, and fortuna…

Great question. Would love to know more about this from those with experience.

Re: Figma removed `window.figma` on view-only pages today

#28

Post by devuo »

diggan wrote: post #25
devuo wrote: post #16

Earlier quoted context omitted.

No need to wait 2 years. Sketch already provides a free web accessible developer handoff tool.

Well, different market really. Afaik, Sketch is still macOS only.

Mac is required for designing, which in pratice most designers are using in the vast majority of organizations, so it's not really an issue.

For feedback and handoff the web tool is free and works in any OS that has a browser.

https://www.sketch.com/handoff/

Re: Figma removed `window.figma` on view-only pages today

#29

Post by alistairSH »

KaiMagnus wrote: post #26

I didn’t know anything was degraded (I’m not the one doing tooling decisions in my org. There were some emails about dev mode, but nothing that really highlighted any impact/changes) until a developer reached out to me a couple weeks ago and wanted to know the names of a couple of icons, colors, etc. The changes were a clear step backwards and this change shows some real pettiness. I guess if you’re on top, money is…

I guess if you’re on top, money is better than goodwill

Otherwise known as "enshittification".

Re: Figma removed `window.figma` on view-only pages today

#30

Post by seumars »

durkie wrote: post #17

So this is kind of tangentially related here, but is there a "state-of-the-art" or best practices on digging through big JS apps / frameworks / objects? Ultimately this is all code running on my machine, so it feels like it should be accessible in the console somewhere . I've had to do a fair amount of this with a Chrome extension I maintain that hooks in to routing (creating bike / running routes) sites, and fortuna…

Not in a way that differs from old-fashioned web scraping. If the website you're targeting is built using a framework and is server-side rendered then it'll most definitely also send all the data it needs for hydrating on the client as JSON, usually attached to the window object as "window.__INITIAL_STATE__" or similar. There are no limits :–)
Post reply on HN