{"action":"created","issue":{"url":"https://api.github.com/repos/developit/preact/issues/619","repository_url":"https://api.github.com/repos/developit/preact","labels_url":"https://api.github.com/repos/developit/preact/issues/619/labels{/name}","comments_url":"https://api.github.com/repos/developit/preact/issues/619/comments","events_url":"https://api.github.com/repos/developit/preact/issues/619/events","html_url":"https://github.com/developit/preact/issues/619","id":218717501,"number":619,"title":"preact ignores/rewrites <img> dimensions?","user":{"login":"Pomax","id":177243,"avatar_url":"https://avatars1.githubusercontent.com/u/177243?v=3","gravatar_id":"","url":"https://api.github.com/users/Pomax","html_url":"https://github.com/Pomax","followers_url":"https://api.github.com/users/Pomax/followers","following_url":"https://api.github.com/users/Pomax/following{/other_user}","gists_url":"https://api.github.com/users/Pomax/gists{/gist_id}","starred_url":"https://api.github.com/users/Pomax/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Pomax/subscriptions","organizations_url":"https://api.github.com/users/Pomax/orgs","repos_url":"https://api.github.com/users/Pomax/repos","events_url":"https://api.github.com/users/Pomax/events{/privacy}","received_events_url":"https://api.github.com/users/Pomax/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":28,"created_at":"2017-04-01T19:28:05Z","updated_at":"2017-04-02T18:15:10Z","closed_at":"2017-04-01T23:37:05Z","body":"I have a React-managed page with some 175+ images, and after switching from `react` to `preact-compat` (using the webpack alias solution) *all* my images come out as `<img src=\"...\" width=\"0\" height=\"0\">` in the DOM, despite having defined dimensions in the JSX source code (e.g. `<img src=\"...\" width=\"100px\" height=\"50px\"/>` etc) - is there any reason why it does this? Because that seems like a pretty crazy bug."},"comment":{"url":"https://api.github.com/repos/developit/preact/issues/comments/291003994","html_url":"https://github.com/developit/preact/issues/619#issuecomment-291003994","issue_url":"https://api.github.com/repos/developit/preact/issues/619","id":291003994,"user":{"login":"developit","id":105127,"avatar_url":"https://avatars1.githubusercontent.com/u/105127?v=3","gravatar_id":"","url":"https://api.github.com/users/developit","html_url":"https://github.com/developit","followers_url":"https://api.github.com/users/developit/followers","following_url":"https://api.github.com/users/developit/following{/other_user}","gists_url":"https://api.github.com/users/developit/gists{/gist_id}","starred_url":"https://api.github.com/users/developit/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/developit/subscriptions","organizations_url":"https://api.github.com/users/developit/orgs","repos_url":"https://api.github.com/users/developit/repos","events_url":"https://api.github.com/users/developit/events{/privacy}","received_events_url":"https://api.github.com/users/developit/received_events","type":"User","site_admin":false},"created_at":"2017-04-02T18:15:10Z","updated_at":"2017-04-02T18:15:10Z","body":"Sorry for missing this discussion - thanks @robertknight for pointing to the previous issue.  Preact can't afford to bundle large whitelists/mappings for DOM edge cases, so right now it uses an `in` check to determine if a property should be used, otherwise falling back to attributes.  That behaviour handles a lot of cases, but is imperfect when DOM properties are mismatched to attributes of the same name.  Technically what Preact is doing is correct here, but it does differ from React and cause a bit of confusion - JSX properties look like attributes, so when they get used to set DOM properties that can be a little odd (even though it's the most common case).\r\n\r\n FWIW, there's a PR in that, if landed, would fix this: https://github.com/developit/preact/pull/511"}}
{"actor":{"display_login":"developit"}}