repository stringclasses 156 values | issue title stringlengths 1 1.01k ⌀ | labels stringclasses 8 values | body stringlengths 1 270k ⌀ |
|---|---|---|---|
facebookreact | devtool react native support reload and profile | Enhancement | react devtool v4 add a new reload and profile feature to measure perf for application mount although it require a bit of hack I don t feel knowledgeable enough about react native to tackle it so my current plan be to just not support this feature for rn if we do decide to support it I think we would need to solve the follow 1 a reload hook on the backend that work for all bundle type not just dev 2 some assurance that the backend will be inject initialize before the first mount commit or a mechanism to delay the first commit like we do in the browser 3 some way for third party code to request a production profiling build similar to how dom do it 4 a sync storage mechanism or some other way for devtool could leave a flag for itself so it know to begin profile immediately after reload connection originally report via |
facebookreact | devtool react native remember save component filter between reload | Enhancement | devtool v4 add a pretty powerful new component filter feature that enable devs to filter out component by type name or file system location because these filter can be a bit elaborate to create they be save between session to improve dev experience unfortunately I don t think I be go to be able to support the persistence functionality for react native in other word filter will be forget each time you reload the app the reason for this be a mix of timing and context the big limit factor be the lack of a synchronous storage option react native have a couple of faux sync storage option but they just in memory wrapper around an async storage layer and they require async initialization that could work if the react native backend wait to initialize devtool until it also initialize the async storage layer but this have implication on reload and profile support 336 originally report via |
facebookreact | devtool occasional fouc when loading devtool | Bug | seem to only happen the first time devtool be open after be instal or perhaps the first time after the browser be open originally report via |
facebookreact | devtool an easy way to see all sibling | Enhancement | I have a particular pattern that I struggle with when navigate deep tree in devtool I want to see all sibling of a node together say I m in the middle of something and I wonder what be all node on the same level it s super hard to actually get to that state I wonder if we could tweak leave button to do that as an intermediate state first press collapse the current node second press collapse all sibling new third press move to the parent maybe this be too crazy or maybe there s another mechanic that can achieve the same effect the goal here be to be able to make sense of the tree structure by go upwards currently implementation detail of child prevent I from see it at least with the expand mode on which be now on by default originally report by gaearon via |
facebookreact | refactor profilercontext to use reducer instead of multi state | Enhancement | the profilercontext be currently comprise of several piece of related state each manage with usestate this necessitate awkward check like this l126 l131 or even bad like this l62 l73 or this l71 l83 this context should be refactore to use a single reducer usereducer like treecontext this be a bit more involved at the moment because of suspense and the profilercontext be high level than the suspense cache although maybe we could work around this by use some sort of subscription l118 l124 see related issue like 16441 and commit 4697f5b |
facebookreact | ssr can not set property memoizedstate of null | Bug | do you want to request a feature or report a bug a bug what be the current behavior can not set property memoizedstate of null if the current behavior be a bug please provide the step to reproduce and if possible a minimal demo of the problem your bug will get fix much fast if we can run your code and it doesn t have dependency other than react paste the link to your jsfiddle or codesandbox example below js const processlink html return rendertostaticmarkup const richtext html const htmlprocesse usememo processlink html html see what be the expect behavior which version of react and which browser os be affect by this issue do this work in previous version of react 16 8 16 9 |
facebookreact | errorboundary render multiple copy of itself when ref assignment fail | Bug | do you want to request a feature or report a bug bug what be the current behavior when a error occur during the assignment of a ref and maybe other condition a error boundary wrap that error may get confused and it render itself multiple time inside the same parent see which render html content error what be the expect behavior html error |
facebookreact | textarea do not show warn when switch from uncontrolled to control like input do | Bug | do you want to request a feature or report a bug bug what be the current behavior while thing like correctly get a warning when switch from uncrontrolled to control I m notice do not if the current behavior be a bug please provide the step to reproduce and if possible a minimal demo of the problem your bug will get fix much fast if we can run your code and it doesn t have dependency other than react paste the link to your jsfiddle or codesandbox example below here s a codesandbox type in the input field we see error correct change to textarea and start over type in field and we don t see the error incorrect I think which version of react and which browser os be affect by this issue do this work in previous version of react 16 8 |
facebookreact | control input make browser not save submit value for autocomplete | Bug | bug behave different per browser but generally inconsistent to uncontrolled input current behavior reproduce with 1 type a in name field and b in uncontrolled field 2 submit 3 re run the fiddle 4 focus input field to see if browser save previous input expect behavior browser provide a suggestion for name and b for uncontrolled field control and uncontrolled element should behave the same actual result uncontrolle input have b suggestion but control input name have no suggestion test on windows 7 google chrome 74 0 3729 169 and on firefox 68 0b4 we can click the workaround button before submit by reset the value dom attribute it behave as expect |
facebookreact | eslint plugin react hook suggest add a dependency on a function that always change | Enhancement | if you write js import react useeffect from react const foo orgid const fetchorg alert orgid useeffect fetchorg orgid return then you get the error react hook useeffect have a miss dependency fetchorg either include it or remove the dependency array but if you follow that advice and add fetchorg to the dep array you get the fetchorg function make the dependency of useeffect hook at line 6 change on every render move it inside the useeffect callback alternatively wrap the fetchorg definition into its own usecallback hook ideally it could suggest the second solution immediately instead of suggest a remediation that it will immediately warn about |
facebookreact | field type email with multiple attribute cursor jump to start | Bug | do you want to request a feature or report a bug bug what be the current behavior while add multiple comma separate email address the cursor will jump to te begin the input field first I think it be a formik issue but it seem to be a react one example pure react example react with formik mdn doc multiple what be the expect behavior cursor stay on current position which version of react and which browser os be affect by this issue do this work in previous version of react chrome 73 safari 12 1 opera 60 0 react 16 7 0 maybe 14551 relate |
facebookreact | profiler mark | Enhancement | can we expose a light weight set of performance mark for people consume browser performance trace e g when a particular profiler commit this should be a lot less heavyweight than the full mark and measure stuff |
facebookreact | memoize component should forward displayname | Enhancement | do you want to request a feature or report a bug I d like to report a bug what be the current behavior first of all thank for the great work on fix however there be still an issue with the current implementation react memo do not forward displayname for test in snapshot component display as and string assertion such as find mymemoizedcomponent win t work what be the expect behavior react memo should forward displayname for the test renderer which version of react and which browser os be affect by this issue do this work in previous version of react react 16 8 5 jest 24 5 0 enzyme 3 9 0 enzyme adapter react 16 1 11 2 n b potentially related to but this be relate to the more recent change to support memo in the test renderer please close if need I m quite new here I d be happy to submit a pr if the issue be not too complex to look into smile |
facebookreact | dangerouslysetinnerhtml be leave empty on client render on top of bad server markup when render html | Bug | this seem to be an edge case of fix in I run into this when try to hydrate content render with ashtml method do you want to request a feature or report a bug bug I think what be the current behavior current behavior 1 server side stuff come in from server and contain the thing we need 2 hydration mismatch happen 3 dangerouslysetinnerhtml be call with correct value but an empty string get render instead I try to replicate the issue on but fail the follow testcase for package react dom src test reactdomserverintegrationelement test js produce the same result I try it first with the same prismicdom richtext ashtml obj call I have in the app but I be not sure if it s correct js test case itrender a div with dangerouslysetinnerhtml set to html insert async render const obj bar const e await render expect e childnode length tobe 1 expect e firstchild tagname tobe li expect e firstchild childnode length tobe 1 bash render a div with dangerouslysetinnerhtml set to html return value of function call with server string render 190ms render a div with dangerouslysetinnerhtml set to html return value of function call with server stream render 52ms render a div with dangerouslysetinnerhtml set to html return value of function call with clean client render 37ms render a div with dangerouslysetinnerhtml set to html return value of function call with client render on top of good server markup 74ms render a div with dangerouslysetinnerhtml set to html return value of function call with client render on top of bad server markup 34ms reactdomserverintegration render a div with dangerouslysetinnerhtml set to html return value of function call with client render on top of bad server markup expect receive tobe expect object be equality expect bar receive what be the expect behavior the client render would have render bar which version of react and which browser os be affect by this issue do this work in previous version of react commit c05b4b8 late master and 16 8 sorry for a bit vague bug report |
facebookreact | react debug tool doesn t support legacy context component contexttype | Bug | original report repro case |
facebookreact | chrome autofill overwrite value on control component | Bug | do you want to request a feature or report a bug report a bug initially report in what be the current behavior autofill overwrite exist value in field when those field be control component in react see to test this add a save address in the chrome option 2019 01 24 10 37 23 what be the expect behavior autofill do not overwrite exist field I ve make a jsfiddle with a plain html form which work with the expected behavior see 2019 01 24 10 37 02 which version of react and which browser os be affect by this issue do this work in previous version of react react 15 3 2 chrome 71 0 3578 98 |
facebookreact | sometimes control email input break in chrome due to punycode | Bug | do you want to request a feature or report a bug report a bug what be the current behavior in chrome when type a sharp s a german letter in an input field with type email it convert the to ss expect unexpected behaviour and the cursor jump back to the beginning of the input field unexpected behaviour this do only happen if the be part of the domain try to type will end as det testss example it can be test with the late google chrome if you don t have a on your keyboard you can reproduce the bug by just copy paste it which version of react and which browser os be affect by this issue do this work in previous version of react test with chrome version 70 0 3538 110 official build 64 bit on ubuntu 18 04 and react 16 6 3 in firefox this do not happen as it do not convert to ss I didn t test other browser |
facebookreact | textarea lose focus after insert pair punctuation with chinese ime | Bug | do you want to request a feature or report a bug bug what be the current behavior textarea lose focus after insert pair punctuation by chinese pinyin 10 key input source on io safari and then textarea can t be focus when I click it but after other element have be focus the textarea could be focus again if the current behavior be a bug please provide the step to reproduce and if possible a minimal demo of the problem your bug will get fix much fast if we can run your code and it doesn t have dependency other than react paste the link to your jsfiddle or codesandbox example below codesandbox demo step youtube video what be the expect behavior just work fine which version of react and which browser os be affect by this issue do this work in previous version of react version of react 16 os ios browser safari |
facebookreact | react test renderer doesn t support suspense and lazy node | Bug | hello how can I test component with suspense lazy now renderer create totree throw totree do not yet know how to handle node with tag 13 react 16 6 1 react test renderer 16 6 1 |
facebookreact | jaw read non interactive element as clickable | Bug | do you want to request a feature or report a bug bug what be the current behavior 1 I create an app use create react app 2 I use jaw professional edition version 2018 build 1710 42 ilm and internet explorer 11 on window 7 3 I use arrow key to navigate to paragraph edit src app js and save to reload 4 jaw announce edit src app js and save to reload clickable what be the expect behavior this paragraph be non interactive it should not be announce as clickable which version of react and which browser os be affect by this issue do this work in previous version of react jaws professional edition version 2018 build 1710 42 ilm internet explorer 11 window 7 create react app 2 0 3 suspect cause use chrome event listener breakpoint I observe there s a function call trapclickonnoninteractiveelement which be the onclick handler for non interactive element this noop function be cause jaw to think this be an interactive element possible solution in trapclickonnoninteractiveelement l245 there be a comment which read todo only do this for the relevant safaris maybe I think that this would fix this issue |
facebookreact | relax tostre consistency guarantee | Enhancement | we recently chat about and related work e g with sebmarkbage and he raise a good point it seem like overall treat they consistently be add significant overhead in the implementation readability and there s undoubtedly runtime overhead to it too there be two separate issue here warn for invalid value ensure that the output for invalid value be consistent e g function be always skip the conclusion we come to be that we should keep warn for bad value but as long as we warn consistency be not necessary it s fine if we sometimes stringify a function and sometimes skip it as long as we always warn for those case our guide principle for invalid input should be that we handle they with the least amount of overhead both at runtime and in term of code size not that they re always handle the same way one exception to this be probably symbol because they throw when stringifie so it seem like skip they be actually desirable unless we re okay with error |
facebookreact | onchange doesn t fire if input re render due to a setstate in a non react capture phase listener | Bug | extract from this issue have always be in react I can reproduce it up to react 0 11 however it s probably extremely rare in practice and isn t worth fix I m just file this for posterity here be a minimal example js class app extend react component state value handlechange e this setstate value e target value componentdidmount document addeventlistener input comment out this line to fix this setstate true render return reactdom render document getelementbyid container type doesn t work unless I comment out that setstate call in the capture phase listener say the input be empty and we re type a what happen here be that setstate in the capture phase non react listener run first when re render due to that first empty setstate input prop still contain the old value while the dom node s value be new a they re not equal so we ll set the dom node value to accord to the prop and remember as the current value then changeeventplugin try to decide whether to emit a change event it ask the tracker whether the value have change the tracker compare the presumably new node value it s we ve just set it early with the lastvalue it have store also and also just update no change our a update be lose we never get the change event and never actually get a chance to set the correct state |
facebookreact | onmousedown cause splash on real io browser | Bug | do you want to request a feature or report a bug bug what be the current behavior unexpected grey splash cause by onmousedown on real io device s browser both safari and chrome please checkout this grey splash issue first I do some trial later and find out that vanilla html btn doesn t cause grey splash but with react s jsx there be a noticeable grey splash what be the expect behavior who want a splash which version of react and which browser os be affect by this issue do this work in previous version of react react 16 3 2 |
facebookreact | unexpected warning when hydrate with portal and ssr | Bug | do you want to request a feature or report a bug bug what be the current behavior give the follow simplify snippet jsx class hovermenu extend react component render if typeof document undefined return null const root document getelementbyid root return reactdom createportal hello world root class para extend react component render return some text where div root be a valid div that exist the follow error be show when hydrate after ssr warn expect server html to contain a matching in the warning go away if I update the definition of hovermenu to jsx class hovermenu extend react component componentdidmount this setstate isactive true render const isactive this state if isactive return null const root document getelementbyid root return reactdom createportal hello world root I d prefer not to do that because of the double rendering cause by setstate in componentdidmount I don t quite understand what that error be tell I no be render server side in either case the error be particularly confusing as the hovermenu dom div be not even render inside a dom span I wonder if this be happen because hovermenu be nest inside a react span what be the expect behavior no error be throw or at least that the error message be clear which version of react and which browser os be affect by this issue do this work in previous version of react chrome 65 react 16 2 ssr through next 5 1 |
facebookreact | react onblur event not fire during unmount | Bug | do you want to request a feature or report a bug bug what be the current behavior if a dom element render by a react component have focus and the react component unmount the react onblur event do not fire on parent dom element if the current behavior be a bug please provide the step to reproduce and if possible a minimal demo of the problem your bug will get fix much fast if we can run your code and it doesn t have dependency other than react paste the link to your jsfiddle or codesandbox example below what be the expect behavior I would expect that just like the browser fire a focusout event when remove a dom node react would fire an onblur event up to parent node when the focused node be remove unmounted which version of react and which browser os be affect by this issue do this work in previous version of react react 16 2 mac os x 10 13 2 browser chrome 67 0 3366 0 chrome 64 0 3282 186 no idea if this work in early version of react |
facebookreact | for control input step do not work as expect unless initialize with null or | Bug | bug what be the current behavior for input type number step do not work as expect if there be an initial value set step only seem to get honor if the initial value be or null example the example use a control input bind value and step step be 1 10th of the value if you edit the value in the textbox to 50000 and increment use the stepper it will increment to 50100 I e by the initial value and not by the current step edit the code so initial value be or null edit textbox to 50000 and step up value go to 55000 as expect what be the expect behavior it should be possible to render a number input that honor step without have to initialize the input component value to null or first it seem when there be an initial value provide it will write a value attribute into the dom e g value 100 when initial value be or null then just the value attribute be write to dom with no assignment e g value which version of react and which browser os be affect by this issue do this work in previous version of react 16 3 0 alpha 1 port to this version to confirm if still an issue 0 14 7 originally find in this version seem to affect chrome only confirm window and mac version 59 and 64 bug do not appear in safari on a mac at least |
facebookreact | consider a more specific warning for key undefined | Enhancement | propose in this comment I have change the casing of i d in the response but forget to commit it aaaaaand I end up with it happen basically I be do key undefined could react warn user when this happen something like look like you try to supply a key but the value supply be undefined check the render and so on I think it might make sense to give a more specific warning in this case open to suggestion about specific wording and in which case it would be use |
facebookreact | backspace fail to clear value on input type email | Bug | do you want to request a feature or report a bug bug what be the current behavior email input doesn t control for whitespace possible variation on issue 6368 however 6368 show up at 15 0 0 this bug show up at 15 2 if the current behavior be a bug demo no bug in react 15 0 0 no bug in react 15 1 0 bug on react 15 2 react 15 fiddle bug on react 16 react 16 fiddle what be the expect behavior when a user press down the backspace key and hold it all value in the input be remove include the whitespace which version of react and which browser os be affect by this issue do this work in previous version of react work on 15 1 0 bug at 15 2 0 testing on chrome 63 macos sierra 10 12 |
facebookreact | number input get clear when type period as decimal mark | Bug | do you want to request a feature or report a bug bug what be the current behavior my os and browser be configure to a locale that use comma as the decimal mark finland for those interested in the codepen below when I accidentally type a period after some number the whole input get clear this be somehow relate to the parent component s state be update because if the defaultvalue prop be remove from the component the input doesn t get clear if the current behavior be a bug please provide the step to reproduce and if possible a minimal demo of the problem via or similar template for react 16 template for react 15 what be the expect behavior the input should retain its visible value even if it would be invalid can t be convert to a number which version of react and which browser os be affect by this issue do this work in previous version of react react 16 2 0 and chrome 63 on macos 10 12 6 test in safari 11 0 2 and type a period kinda work after type the first number after the period it get convert to a comma but the cursor jump to the beginning also test in firefox 57 0 1 but it seem to think that period be the correct decimal mark |
facebookreact | react do not call onblur callback | Bug | do you want to request a feature or report a bug bug what be the current behavior when input control become disabled react do not call onblur callback if the current behavior be a bug please provide the step to reproduce and if possible a minimal what be the expect behavior 1 focus on input element 2 press enter button it make input disabled 3 blur counter and native blur counter should be equal |
facebookreact | value defaultvalue symbol function should be ignore not stringifie | Bug | regression in master from find it thank to the attribute fixture snapshot |
facebookreact | reset a form contain a focus control number input put it out of step with state | Bug | here s a fixture demonstrate the issue first test case if you have a control number input within a form contain a reset button hit enter can trigger that reset event this cause the focused input to be reset to the defaultvalue which win t be in sync with the track value because we do that work on blur for number input to avoid trigger validation warning this doesn t affect other input type since the track value be update immediately this might be a viable tradeoff for avoid those validation warning so I m not sure if this be actionable but I want to at least document it for future reference cc nhunzaker gaearon |
facebookreact | rfc drop isattributenamesafe check | Enhancement | we currently validate dom attribute on the client and ignore the one with invalid name l202 l204 this check use to be important for safety when we do innerhtml render on the client side but it s not anymore if we just let it call setattribute the browser would throw on a bad attribute name this check use to run very infrequently only for datum attribute and custom element but now more attribute follow this code path since any simple attribute with the same name be effectively treat as unknown attribute so even though we cache the result it seem unfortunate to do the work that the browser be already do for we while this would be a break change so it have to go in 17 I think we should just remove this check and let the browser throw this do make spread prop blindly a bit more dangerous but we have a warning so it should be visible |
facebookreact | reword unknown property warning to be less obnoxious | Enhancement | I think before it might cause knee jerk reaction and it do in practice I think we should change the phrasing to a more neutral one potentially explain why we prefer camel case |
facebookreact | type fiber by tag as disjoint union | Enhancement | sebmarkbage try this in but flow couldn t handle it well might be worth try again someday |
facebookreact | multiple onfocus event fire on single focus in safari | Bug | I d like to report a possible bug 1 brief description onfocus synthetic event be fire multiple time on single focus occurrence in safari expect behaviour be for it to be fire only once per focus 2 live demo 3 minimal step to reproduce install create react app npm install g create react app create an example application create react app input focus test cd input focus test edit application file and add input with onfocus event handler vi src app js javascript import react component from react import logo from logo svg import app css class app extend component handleonfocus evt console log handleonfocus evt render return welcome to react to get start edit src app js and save to reload input export default app start application npm run start open up locahost 3000 in safari click on the input field with developer s console open notice focus event fire multiple time 4 additional info this issue have be find in the follow environment macos sierra version 10 12 6 also test and find on high sierra safari 10 1 2 also test and find in safari 10 0 and safari 11 seem to work on late safari mobile chrome and firefox react js 15 5 4 also test and find in react 16 example step to reproduce above generate with create react app version 1 4 1 some of our observation that might come in handy this issue seem to behave randomly to some extent event be usually fire twice when change focus from input to input so first click on input fire two event consequential fire only one but when change focus to a different input field it fire twice again additional interesting behavior happen with multiple input field for instance with input field 1 and 2 first focus on input 1 generate two event onfocus with input 1 but then focus on input 2 sometimes generate three event onfocus with input 1 then input 2 then input 1 again as target |
facebookreact | form restoration react hydration | Bug | do you want to request a feature or report a bug bug reproduction 1 open see the source 2 open 3 fill in the input for example you can type foo 4 press submit 5 undo the navigation 6 see how the input value be outdate it doesn t match what s inside the textbox what be the current behavior let s say you start fill a form input type text or a select element with foo then you click on a link and press the back button the browser back forward cache or maybe the form restauration logic will kick in and change the initial value of the form element you will get the foo value back in the input however react doesn t account for it when the component be control for end user it mean that they will try to submit a form because they see value in the input but it win t work they need to go back to each field and make a fake change so that react register it this issue could also be work around by not control the input but I m not sure how popular form library handle this what be the expect behavior I expect react to trigger an onchange event to replicate the actual form value at the fundamental level there be a coordination issue between the browser and react which version of react and which browser os be affect by this issue do this work in previous version of react react late v18 2 0 chrome late v112 0 detail we have be use the following hack on material ui js componentdidmount fix ssr issue with the go back feature of the browser let s say you start fill the input with foo you change the page then after come back the browser will reset the input value to foo but we also need to tell react about it this handlechange target this input but it come with issue so instead we try simulate a change event as suggest in stack overflow but it doesn t work anymore js var event new event input bubble true element dispatchevent event so for now we be go to disable the cache with |
facebookreact | mouseenter event not trigger when cursor move from disabled button | Bug | bug mouseenter event not trigger when cursor move from disabled button see example playground code 3cdiv 3e 0a 20 0a 20 20 20 20 3cdiv 20classname row 3e 0a 20 20 20 20 20 20 20 20hover 20on 20 20right 20button 20and 20then 20move 20cursor 20to 20left 20button 0a 20 20 20 20 20 20 20 20 3cdiv 3e 0a 20 20 20 20 20 20 20 20 20 20 20 20 3cbutton 20onmouseenter 7b 3e 7balert hey 7d 7d 20 3e 0a 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20not 20disabled 0a 20 20 20 20 20 20 20 20 20 20 20 20 3c button 3e 0a 20 20 20 20 20 20 20 20 3c div 3e 0a 20 20 20 20 20 20 20 20 3cdiv 3e 0a 20 20 20 20 20 20 20 20 20 20 20 20 3cbutton 20disabled 7b 20true 20 7d 3edisabled 3c button 3e 0a 20 20 20 20 20 20 20 20 3c div 3e 0a 20 20 20 20 3c div 3e 0a 0a 20 20 20 20 3cdiv 20classname row 3e 0a 20 20 20 20 20 20 20 20hover 20on 20 20right 20button 20and 20then 20move 20cursor 20to 20left 20button 0a 20 20 20 20 20 20 20 20 3cdiv 3e 0a 20 20 20 20 20 20 20 20 20 20 20 20 3cbutton 20onmouseenter 7b 3e 7balert hey 7d 7d 20 3e 0a 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20not 20disabled 0a 20 20 20 20 20 20 20 20 20 20 20 20 3c button 3e 0a 20 20 20 20 20 20 20 20 3c div 3e 0a 20 20 20 20 20 20 20 20 3cdiv 3e 0a 20 20 20 20 20 20 20 20 20 20 20 20 3cbutton 3enot 20disabled 3c button 3e 0a 20 20 20 20 20 20 20 20 3c div 3e 0a 20 20 20 20 3c div 3e 0a 20 0a 3c div 3e what be the expect behavior should trigger mouseenter event react 15 5 3 late chrome macos 10 12 5 |
facebookreact | false positive getdefaultprop warn when mix development and production version | Bug | as migrate from 15 4 to 15 5 I be rewrite original react component with create react class however there be a warning react 15 5 4 js bust 1497843639843 3287 warning getdefaultprop be only use on classic react createclass definition use a static property name defaultprop instead as I be really transfer from a classic react createclass definition I would like to ask be this warning appropriate or this be a depreciation same as the level of migrate to create react class ooop I get ticket 9999 d |
facebookreact | error when source be provide to production build | Enhancement | currently if the source transform be enable together with the production build there be no indicator of a poorly performant configuration even have it we already check for the existence of a source field l203 so we can just reuse the same check to issue something in prod mode if it exist the problem be that we don t have any warning module in prod and it be unclear if it would get attention or even consider to spammy in prod we could throw but that might be too extreme since a misconfiguration would kill the site we could also use this to set a flag on the react devtool global hook object the icon in the devtool extension could use this to indicate a misconfigured build |
facebookreact | a number input will always have leave pad 0 though parsefloat value in onchange | Bug | do you want to request a feature or report a bug bug what be the current behavior I have a number input with defalut value 0 and in onchange function I ll parse value to float to avoid invalid input but I ll always get leave pad 0 on input ui but in previouse version my code work if the current behavior be a bug please provide the step to reproduce and if possible a minimal demo of the problem via or similar template this setstate value parsefloat e target value parsefloat e target value 0 what be the expect behavior should not have leave pad 0 which version of react and which browser os be affect by this issue do this work in previous version of react react 15 5 3 all browser all os it work in 15 4 2 |
facebookreact | no blur event fire when button be disabled remove | Bug | do you want to request a feature or report a bug bug what be the current behavior when a focusse button become disabled react do not dispatch a blur event if the current behavior be a bug please provide the step to reproduce and if possible a minimal demo of the problem via or similar template 1 attach a blur event to a button 2 focus the button 3 make the button disabled or remove it from the dom what be the expect behavior a blur event will be dispatch which version of react and which browser os be affect by this issue do this work in previous version of react 15 1 0 not sure if it work in previous version isolate test case |
facebookreact | event preventdefault in click handler do not prevent onchange from be call | Bug | do you want to request a feature or report a bug bug what be the current behavior when render an input element of type checkbox with an onclick and onchange handler onchange be still call even though event preventdefault be call in the onclick handler if the current behavior be a bug please provide the step to reproduce and if possible a minimal demo of the problem via or similar template what be the expect behavior call event preventdefault in the onclick handler should prevent the default action from occur or undo its effect which be to update the value of the input element this should stop any change event listener from be invoke see for expect behavior which version of react and which browser os be affect by this issue do this work in previous version of react test use a build from master macos 10 12 2 verify in chrome 56 0 2924 87 64 bit firefox 51 0 1 64 bit safari 10 0 2 call the change event listener in both case |
facebookreact | clear button on io date input do not return correct event value | Bug | bug for io only when press clear on a date input the onchange event be fire but event target value be show the original value rather than an empty string what be the current behavior on chrome and android when the clear button be press the onchange event have a value of on io when the clear button be press the onchange event have a value of previousvalue demo try on chrome android then on io what be the expect behavior value should be return an an empty string version affect react 15 io 10 unsure of previous version |
facebookreact | undo behavior in control textarea work differently from the default behaviour in chrome | Bug | if you control a textarea with value it behave differently when you use undo when the textarea be control you can only undo one letter at a time this be not how undo work normally with an uncontrolled component undo seem to work as expect with input component with a control textarea component you can only undo one letter at a time the normal undo work with some kind of algorithm for how much be go to be un or redone you can try the difference in this codepen test with react 15 3 1 and chrome 54 and chrome canary work as expect in firefox and safari it might be a chrome bug |
facebookreact | fiber formalize state | Enhancement | in fiber there be a number of state that a component can be in however it be not formalize in the code right now instead the state be infer this lead to hard to follow code instead we can organize the code in term of explicit state which be what the original prototype do before componentdidmount I e current null never begin have be begin before but never complete have be complete before not commit but hasn t begin this time around begin but not yet complete complete but not yet commit after componentdidmount I e current null haven t begin an update yet have be begin before but never complete an update have be complete before not commit but hasn t begin this update begin update but not yet complete complete update but not yet commit the child set of a component also have some state never reconcile the current set last commit a previously reconcile set that hasn t commit yet |
facebookreact | input autofocus cause focus to be emit before ref | Bug | can reproduce on chrome but not in ie11 |
facebookreact | bug click not disabled on alert click click I | Bug | bug in the follow jsx const component alert click by react click I here and here click on click I here and will not trigger alert click by react whereas click on the red here will trigger alert click by react demo thank for react it s an incredibly well design tool |
facebookreact | attach stack at setstate call in dev mode | Enhancement | we have a queue for state transition there be a natural place for a new error stack frame to be store there we could use this information to work our way back from error to show information about which setstate call be the source of the error because of batch it be not always possible to make the correct attribution it could be one of several possible source specifically I d like to use this in fiber when the starvation protection kick in we can show which state transition be keep get defer due to high priority work |
facebookreact | ie 11 and edge no long prompt to remember password on control form | Bug | do you want to request a feature or report a bug bug regression ie edge what be the current behavior on react v15 2 0 edge and ie11 do not prompt the user to save the password for the form step to reproduce with react 15 1 0 with react 15 2 0 what be the expect behavior the browser prompt the user to save their password for the form which version of react and which browser os be affect by this issue do this work in previous version of react react 15 2 0 it work in react 15 2 0 ie 11 edge |
facebookreact | onmouseenter propagation in double reactroot | Bug | I think it be bug now onmouseenter event handler call in child element when there be several reactroot to reproduce run fiddle and move mouse from white square to red and back in console you can see log when you do it link it work wrong expect behavior handler have to call just when mouse enter to red square see here simiar example but with one reactroot it work right react 15 1 0 |
facebookreact | change state in onfocus and onchange for a select multiple element do not work in firefox | Bug | I want to use a control component in react in addition to the value I also want to keep the focused state of the select in the state to do this I update the state with setstate in the onchange onfocus and onblur event handler unfortunately there be an issue in firefox firefox will only update the value on a change event after the select have gain focus this mean that a user have to click twice on the select element to change its value when it do not have focus I would expect the select to gain focus and change the value at the same click I create a jsfiddle to demonstrate the prolem react select multiple issue in firefox demonstration I only see this problem in firefox and with select multiple in ie and chrome it be work as expect and in firefox it be work as expect for other form element simple select checkbox radio text input textarea my environment firefox 46 0 1 under win7 x64 react 15 1 0 |
facebookreact | onmouseleave doesn t work if the node get detach | Question | I have a problem with this kind of component javascript class onhover extend component constructor prop super prop this state bool false render return this setstate bool true onmouseleave this setstate bool false this state bool option1 show after onmouseenter option2 show after onmouseleave notice that the first option1 be a span option2 be a div this work fine when I move the mouse slowly though if I cut through this with the mouse very fast only the onmouseenter event get trigger but not the onmouseleave event it be always work though if both option have the same tag if both be div or both be span edit I think it have something to do with rerendere when the component be of the same type but I force a rerender it cause the same issue javascript class onhover extend component constructor prop super prop this state bool false render return this setstate bool true onmouseleave this setstate bool false this state bool option1 show after onmouseenter option2 show after onmouseleave |
facebookreact | rfc configure warning level use env variable | Enhancement | would it be feasible to specify the version of warning you want through a static environment variable that would silence new warning so that you can safely update minor version without worry about warn spew dynamic configuration create stateful share module dependency which we re very close to get rid of for the isomorphic package reactcurrentowner be the last one |
facebookreact | iframe load event not fire in chrome and safari when src be about blank | Bug | see it will not trigger the alert in chrome and safari but it will work in firefox and even ie8 be this a react issue or webkit issue if it be a webkit issue should we fix it in react give that we want consistent event across browser ps the jsfiddle be base on the isuse 5332 |
facebookreact | form input name nodename break onsubmit event handle | Bug | it happen that I stumble on follow edge case if you add name nodename attribute to form s input at some point of react event handle changeeventplugin js shouldusechangeevent it will call elem nodename elem nodename tolowercase but coincidentally nodename property refer to input and invocation fail here s a jsfiddle example |
facebookreact | onrespondergrant call before onresponderterminate | Bug | when a responder capture the active responder it seem that onresponderterminate be not call until after onrespondergrant this seem like the wrong thing to do are there reason for this behavior |
facebookreact | datatransfer s dropeffect not work on ie edge with not minify version react js | Bug | code exmaple non minified version and minify version both have the same code html and js the only difference be reference to different version of react js file there be three box drag the drag I box will show a start at the top then show a over if it be drag over either normal drop or drop react box and show a end with a drop to the two drop box everything work fine on my firefox 43 0 1 and the the minified version work fine on my ie 11 and edge 13 the only thing dose not work be the non minified version on ie edge when drag over the drop react box there show no over in the f12 console I can see line of script16389 unspecified error and with console log ev datatransfer I get this result object datatransfer dropeffect effectallowe all file filelist item datatransferitemlist type domstringlist I think the dropeffect should also be accessible on ie edge with non minified version react js file |
facebookreact | use inline event handler for trapbubbledeventslocal and the io safari click hack | Enhancement | we currently do a lot of work at the end of mount to find all the node and attach listener after the fact this be severely impacting initial rendering performance of and click handler instead we can just use inline event handler in the innerhtml string for the ios safari hack it should be trivial the handler doesn t even have to do anything the inline event handler would need to either redispatch the event or call into some other event handler system probably a global listener js window handlereactevent html since there could potentially be multiple react they should probably chain the handler if there already be one register although multiple react in the same document be already pretty broken in this regard it doesn t have to be a global since inline event handler get the element add as a with element scope around itself it be equivalent to add it to the prototype js element prototype handlereactevent or js htmlimgelement prototype handlereactevent this make they a bit more hidden unobtrusive we still need to render this string for server side rendering to avoid need to change the html or wire up handler after the fact on the client since these event can fire before react have load we need to check for the existence of the handler before it be use js it be critical that this string be short for innerhtml string concat performance and network performance yet it need to be unlikely to collide with anything else be there a unicode character we could use |
facebookreact | change event fire extra time before ime composition end | Bug | extra detail similar discussion with extra detail and reproduce analysis previous attempt to fix it include some unit test but sufficient to be confident in the fix original issue when I be try this example from any chinese character inputte by chinese pinyin input method would fire too many render like screen shoot 2015 05 21 at 14 04 36 actually I would expect those not to fire before I confirm the chinese character then I try another kind of input method wubi input method I get this screen shoot 2015 05 21 at 14 17 15 it s weird too so I do a test in jquery screen shoot 2015 05 21 at 14 05 12 only after I press the space bar to confirm the character the keyup event would fire I know it might be different between the implementation of jquery keyup and react onchange but I would expect the way how jquery keyup handle chinese character instead of react s onchange |
facebookreact | geteventkey implementation inconsistent with dom3 spec firefox implementation | Bug | there be some inconsistency between geteventkey and the dom3 keyboard event spec as well as what firefox have implement key property be not correctly set for printable character on keydown and keyup event this work properly in firefox and my interpretation of the standard be that firefox s behaviour be correct here from the spec if the key generate a printable character and there exist an appropriate unicode code point then the keyboardevent key attribute must be a string consist of the char value of that character enter key only fire keydown in firefox but fire both keydown and keypress in chrome this should be consistent across browser capslock key only fire keydown when it be toggle on when cap lock be toggle from on to off no keydown event be fire this may be a browser limitation in chrome repro test this page in firefox and compare the result to chrome |
facebookreact | touchmove doesn t fire on remove element | Enhancement | if you have this state show such that the ontouchstart handler remove the div and maybe replace it with another one in the same place useful in certain draggable interaction the ontouchmove handler doesn t fire because the event of a detach element no long bubble to document we should probably bind the touchmove handler when the element receive touchstart instead of delegate to document sort of relate to 1254 cc merb eater |
facebookreact | iframe content cause invariant violation | Bug | when use server render put an in an seem to invariably cause an invariant violation it can t find the image this be relate to 1252 but not identical in both case the browser isn t aware of the inner element however in this case it s because browser that support iframe be actually mutate the dom by replace the content with the document specify in the src attribute |
facebookreact | provide a way to handle browser autocomplete form value on control component | Bug | when there s a control component for form name that the user have save in their browser common with username password field the browser will sometimes render the page with value in those field without fire onchange event if the user submit the form the component state do not reflect what be show to the user in experiment with this it appear that the datum be there on load test by log this refs myinput getdomnode value |
facebookreact | bug useformstate formaction become null in strict mode | Bug | the form action return from the hook useformstate become null when use react strict mode it cause the page to reload on the submission of the form and the action do not work I know that the react strict mode perform some action twice intentionally to find unexpected behavior in the development but it would be well if we could use it without disable the strict mode react version 0 0 0 experimental bb0944fe5 20240313 step to reproduce 1 enable strict mode 2 submit the form that use form action return from useformstate link to code example the current behavior form action become null cause the page to reload the expect behavior form action should be a function provide as the argument in the useformstate hook |
facebookreact | devtool bug can not remove node 1455 because no matching node be find in the store | Bug | website or app find it on my localhost website repro step I add strictmode on my react app on the top level component adopt I folder structure look like that how often do this bug happen every time devtool package automate react devtool extension devtool version automate 5 0 0 993c4d003 error message automate can not remove node 1455 because no matching node be find in the store error call stack automate text at chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 1 1130512 at c emit chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 1 1099142 at chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 1 1100830 at bridgelisten chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 1 1501127 error component stack automate no response github query string automate text remove node because no matching node be find in the store in title be issue be open be public label component developer tool repo facebook react |
facebookreact | devtool bug memory leak when not use the extension | Bug | website or app repro step 1 use firefox normally not open the browser dev tool at all 2 notice that the browser be get sluggish due to continual gc and that firefox indicate that browser extension be use 2gib 3 disable react dev tool and observe immediate improvement in memory usage and gc cpu usage about memory diff before and after disable react dev tool extension pid nnn explicit allocation 1 894 73 mb 100 0 explicit 1 684 24 mb 88 89 js non window 1 669 75 mb 88 13 zone zone 0xnnn 1 610 78 mb 85 01 realm system principal share jsm global 1 610 79 mb 85 01 class 451 06 mb 23 81 class map object 360 85 mb 19 04 malloc heap 360 85 mb 19 04 misc 0 00 mb 00 00 slot 90 21 mb 04 76 gc heap 360 87 mb 19 05 class function object 360 87 mb 19 05 gc heap 0 00 mb 00 00 malloc heap slot 219 10 mb 11 56 class object object 167 54 mb 08 84 gc heap 51 56 mb 02 72 malloc heap 51 56 mb 02 72 slot 0 00 mb 00 00 element normal 212 20 mb 11 20 class set object 167 09 mb 08 82 malloc heap 167 09 mb 08 82 misc 0 00 mb 00 00 slot 45 10 mb 02 38 gc heap 161 10 mb 08 50 class call object gc heap 115 99 mb 06 12 class lexicalenvironment object 115 99 mb 06 12 gc heap 0 00 mb 00 00 malloc heap slot 45 34 mb 02 39 class array object 45 34 mb 02 39 gc heap 0 00 mb 00 00 malloc heap slot 45 11 mb 02 38 class proxy object gc heap 0 01 mb 00 00 6 tiny 0 01 mb 00 00 5 tiny 40 03 mb 02 11 compartment 40 03 mb 02 11 cross compartment wrapper table 0 00 mb 00 00 private datum 18 94 mb 01 00 19 tiny 14 49 mb 00 76 3 tiny 137 46 mb 07 25 window object 138 79 mb 07 33 top moz extension 98c06d52 ba9c 4097 8d95 cfd0565b93d5 generate background page html i d nnn 135 99 mb 07 18 active window moz extension 98c06d52 ba9c 4097 8d95 cfd0565b93d5 generate background page html 135 73 mb 07 16 js realm moz extension 98c06d52 ba9c 4097 8d95 cfd0565b93d5 generate background page html 135 72 mb 07 16 class 90 48 mb 04 78 class function object 90 48 mb 04 78 gc heap 0 01 mb 00 00 malloc heap slot 45 10 mb 02 38 class call object 45 10 mb 02 38 gc heap 0 00 mb 00 00 malloc heap slot 0 13 mb 00 01 4 tiny 0 01 mb 00 00 sundrie 0 26 mb 00 01 3 tiny 2 80 mb 00 15 js zone 0xnnn 1 33 mb 00 07 8 tiny 73 74 mb 03 89 heap overhead 59 05 mb 03 12 bin unuse 26 77 mb 01 41 bin 128 19 63 mb 01 04 bin 80 12 65 mb 00 67 44 tiny 14 70 mb 00 78 2 tiny 0 71 mb 00 04 7 tiny unfortunately due to I m unable to get any more detail on what exactly be consume all this memory how often do this bug happen every time devtool package automate no response devtool version automate no response error message automate no response error call stack automate no response error component stack automate no response github query string automate no response |
facebookreact | devtool bug consistent memory leak when refresh on react non react website | Bug | website or app repro step with chrome version 121 0 6167 184 official build arm64 react dev tool 5 0 create from revision 993c4d003 on 12 5 2023 repeatedly refresh continually leak memory with react dev tool some memory be retain temporarily between refreshe but notably force gc the trashcan button never shrink each subsequent refresh monotonically increase memory overhead without react dev tool force gc without react dev tool drop the memory footprint from 100 mb to 10 mb instantly other debugging go down a massive rabbithole of chrome version bisection memory between refreshed start to be retain a bit long with this v8 gc change but it always gc d correctly when be force other note this be in incognito mode without any other extension enable happy to provide heap snapshot it appear that retain memory be mostly closure compile code hopefully this should be simple to repro how often do this bug happen every time devtool package automate no response devtool version automate no response error message automate no response error call stack automate no response error component stack automate no response github query string automate no response |
facebookreact | devtool bug big memory leak | Bug | website or app repro step my firefox seriously slow down I try to track down why it turn out an extension be take near 70 gb I make a memory dump to see the issue explicit allocation 75 498 45 mb 100 0 explicit 38 653 19 mb 51 20 js non window 36 174 13 mb 47 91 window object 36 021 81 mb 47 71 top moz extension 0547e6cd 9505 4377 9aed 8126cfe099f6 generate background page html i d 75 34 190 45 mb 45 29 js zone 0x1cb6863ec00 34 010 77 mb 45 05 string 34 005 90 mb 45 04 string length 26970 copy 621562 datum image svg xml base64 pd94bwwgdmvyc2lvbj0im truncate 33 991 67 mb 45 02 malloc heap two byte 14 23 mb 00 02 gc heap two byte 4 87 mb 00 01 13 tiny 179 68 mb 00 24 9 tiny 1 831 36 mb 02 43 active window moz extension 0547e6cd 9505 4377 9aed 8126cfe099f6 generate background page html 1 831 28 mb 02 43 js realm moz extension 0547e6cd 9505 4377 9aed 8126cfe099f6 generate background page html 1 831 27 mb 02 43 class 934 56 mb 01 24 class object object 896 70 mb 01 19 4 tiny 0 01 mb 00 00 sundrie 0 08 mb 00 00 3 tiny 152 31 mb 00 20 22 tiny 671 13 mb 00 89 24 tiny I know it be react dev tool with it s extension i d 547e6cd 9505 4377 9aed 8126cfe099f6 when I decode the svg of the string that I truncate I immediately recognize my own dark mode switch trick I know the image be use on and I have both tab open and it doesn t reproduce at will it s probably the first link since it use react how often do this bug happen sometimes devtool package automate no response devtool version automate no response error message automate no response error call stack automate no response error component stack automate no response github query string automate no response |
facebookreact | name property be not define for option in the animation color dropdown | null | react version 16 8 0 step to reproduce 1 open react select react select com 2 navigate to the custom style 3 navigate to animation dropdown 4 observe whether name property be define for option in the animation color dropdown or not link to code example react select react select com the current behavior name property be not define for option in the animation color dropdown the expect behavior name should be define for option in the animation color dropdown attachment name not define screen reader behavior react |
facebookreact | feat I hope react support two instruction r if and r for | null | I think there be a reason for this although react provide the great flexibility base on js and provide the good support for complex page for simple need some less intuitive writing method be often require I think it support something like xxx be very good but only these two be enough if there be too many and provide scalable interface it may violate the original intention of simplify programming and fall into the trap of vue s complex instruction set in a trap |
facebookreact | bug react get runtime error when user break the rule of hook instead of tell user what to do | null | react version 18 2 0 step to reproduce 1 open the link below it will show a page with a button 2 click the button and you will get the error link to code example the current behavior user get a runtime error can not read property of undefined reading length this be because react use different datum structure in memoizedstate e g object for useeffect array for usecallback if user break the rule of hook the follow code will crash which will confuse user ts function updatecallback callback dep if nextdep null var prevdep prevstate 1 1 prevstate be now an object if arehookinputsequal nextdep prevdep 2 pass an undefined here return prevstate 0 function arehookinputsequal nextdep prevdep if nextdep length prevdep length 3 this will crash prevdep be undefined error the final argument pass to s change size between render the order and size of this array must remain constant n n previous s n incoming s currenthooknameindev prevdep join nextdep join the expect behavior user should receive a react message like other scenario that break the rule of hook render more hook than during the previous render actually if we modify the last hook from usecallback to useeffect we can get this message eslint can not identify this scenario and will not report error if it s not the responsibility of react at least the eslint plugin react should detect it |
facebookreact | devtool bug could not find node with i d 24823 in commit tree | Bug | website or app react native app repro step recode profile how often do this bug happen every time devtool package automate react devtool core devtool version automate 4 28 0 9b95b131b error message automate could not find node with i d 24823 in commit tree error call stack automate text at c user khhus appdata roam npm node modules react devtool node modules react devtool core dist standalone js 2 1024248 at map foreach at c user khhus appdata roam npm node modules react devtool node modules react devtool core dist standalone js 2 1024197 at ar getrankedchartdata c user khhus appdata roam npm node modules react devtool node modules react devtool core dist standalone js 2 1024665 at oc c user khhus appdata roam npm node modules react devtool node modules react devtool core dist standalone js 2 1236925 at en c user khhus appdata roam npm node modules react devtool node modules react devtool core dist standalone js 2 40150 at ci c user khhus appdata roam npm node modules react devtool node modules react devtool core dist standalone js 2 58285 at es c user khhus appdata roam npm node modules react devtool node modules react devtool core dist standalone js 2 116447 at el c user khhus appdata roam npm node modules react devtool node modules react devtool core dist standalone js 2 100131 at bl c user khhus appdata roam npm node modules react devtool node modules react devtool core dist standalone js 2 100060 error component stack automate text at oc c user khhus appdata roam npm node modules react devtool node modules react devtool core dist standalone js 2 1236682 at div at div at div at yo c user khhus appdata roam npm node modules react devtool node modules react devtool core dist standalone js 2 1145723 at c user khhus appdata roam npm node modules react devtool node modules react devtool core dist standalone js 2 1354530 at hs c user khhus appdata roam npm node modules react devtool node modules react devtool core dist standalone js 2 1161269 at c user khhus appdata roam npm node modules react devtool node modules react devtool core dist standalone js 2 1163988 at div at div at div at ms c user khhus appdata roam npm node modules react devtool node modules react devtool core dist standalone js 2 1163822 at rc c user khhus appdata roam npm node modules react devtool node modules react devtool core dist standalone js 2 1226474 at zu c user khhus appdata roam npm node modules react devtool node modules react devtool core dist standalone js 2 1218933 at lt c user khhus appdata roam npm node modules react devtool node modules react devtool core dist standalone js 2 1068120 at t c user khhus appdata roam npm node modules react devtool node modules react devtool core dist standalone js 2 1095397 at ts c user khhus appdata roam npm node modules react devtool node modules react devtool core dist standalone js 2 1167737 at r c user khhus appdata roam npm node modules react devtool node modules react devtool core dist standalone js 2 1361060 github query string automate text not find node with i d in commit tree in title be issue be open be public label component developer tool repo facebook react |
facebookreact | the error be throw at at ee emit at at at array foreach at be onmessage bug can not add node 1 because a node with that i d be already in the store | Bug | website or app localhost repro step the error be throw at at ee emit at at at array foreach at am onmessage how often do this bug happen every time devtool package automate react devtool core devtool version automate 4 27 2 7f747b80e error message automate can not add node 1 because a node with that i d be already in the store error call stack automate text at at ee emit at at at array foreach at am onmessage error component stack automate text the error be throw at at ee emit at at at array foreach at am onmessage github query string automate text add node because a node with that i d be already in the store in title be issue be open be public label component developer tool repo facebook react |
facebookreact | devtool bug there be a problem with the scrollbar in | Bug | website or app repro step in learn react section below there be various heading like describe the ui add intereactivity when select one of they then scrollbar appear when try to hold this scrollbar be get hide and when hover away from this scrollbar be reapear screenshot 25 screenshot 24 how often do this bug happen every time devtool package automate no response devtool version automate no response error message automate no response error call stack automate no response error component stack automate no response github query string automate no response |
facebookreact | devtool bug console log in second call to usememo callback in strict mode be not dim or suppress | Bug | website or app repro step this only happen in the canary version of react most likely due to the change make in 25583 to repro 1 enable strict mode 2 call console log from inside a usememo callback e g js usememo console log usememo callback in react 18 2 0 the log from the second strict mode call to the usememo callback will be dim or suppress depend on devtool setting in react 18 3 0 canary 60a927d04 20240113 or nextjs 14 0 4 both call be log normally note when use codesandbox to repro look at the log from the browser devtool console not the embed one in codesandbox which doesn t always show the same output how often do this bug happen every time devtool package automate no response devtool version automate no response error message automate no response error call stack automate no response error component stack automate no response github query string automate no response |
facebookreact | devtool bug memory leak | Bug | website or app unkneon repro step unknwon for I I can t figure out where the leak be from or what website its from but it happen everytime so its just bootup firefox with react devtool on browse for an hour or so lose 5gigs of memory how often do this bug happen every time devtool package automate no response devtool version automate no response error message automate no response error call stack automate no response error component stack automate no response github query string automate no response |
facebookreact | devtool bug can not read property of undefined read concat | Bug | website or app on a localy host react app v18 2 0 repro step after record a profil in the profiler panel I click on the graph in the top right corner how often do this bug happen every time devtool package automate react devtool extension devtool version automate 5 0 0 993c4d003 error message automate can not read property of undefined read concat error call stack automate text at updatetree chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 1 1114468 at getcommittree chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 1 1113282 at rr getcommittree chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 1 1116473 at commitflamegraphautosizer chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 1 1353046 at lf chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 1 40670 at gh chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 1 61725 at yn chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 1 118951 at rk chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 1 103877 at qk chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 1 103805 at df chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 1 103623 error component stack automate text at commitflamegraphautosizer chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 1 1352847 at div at div at div at settingsmodalcontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 1 1253868 at chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 1 1484419 at bo chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 1 1271707 at div at div at themeprovider chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 1 1274418 at chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 1 1274615 at div at div at div at themeprovider chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 1 1274418 at timelinecontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 1 1344475 at profilercontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 1 1336084 at treecontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 1 1166113 at settingscontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 1 1194207 at modaldialogcontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 1 1278876 at devtool devtool chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 1 1492154 github query string automate text read property of undefined read concat in title be issue be open be public label component developer tool repo facebook react |
facebookreact | devtool bug can not add node 20 because a node with that i d be already in the store | Bug | website or app repro step uncaught error can not add node 20 because a node with that i d be already in the store the error be throw at chrome extension gpphkfbcpidddadnkolkpfckpihlkkil build main js 1 1128815 at c emit chrome extension gpphkfbcpidddadnkolkpfckpihlkkil build main js 1 1099142 at chrome extension gpphkfbcpidddadnkolkpfckpihlkkil build main js 1 1100830 at bridgelisten chrome extension gpphkfbcpidddadnkolkpfckpihlkkil build main js 1 1501170 how often do this bug happen every time devtool package automate react devtool extension devtool version automate 5 0 0 993c4d003 error message automate can not add node 20 because a node with that i d be already in the store error call stack automate text at chrome extension gpphkfbcpidddadnkolkpfckpihlkkil build main js 1 1128815 at c emit chrome extension gpphkfbcpidddadnkolkpfckpihlkkil build main js 1 1099142 at chrome extension gpphkfbcpidddadnkolkpfckpihlkkil build main js 1 1100830 at bridgelisten chrome extension gpphkfbcpidddadnkolkpfckpihlkkil build main js 1 1501170 error component stack automate no response github query string automate text add node because a node with that i d be already in the store in title be issue be open be public label component developer tool repo facebook react |
facebookreact | devtool bug hook parse fail if a hook use usesyncexternalstore | Bug | website or app repro step 1 open up this page source 2 open up the react dev tool 3 navigate to the component tab 5 observe in the right sidebar that hook name parse fail for one of the two component hook name parsing be really helpful when debug optimize large component with lot of hook and this issue make that feature unusable on component whose hook make use of usesyncexternalstore this be particularly painful for my current work where nearly all component make use of zustand store which use usesyncexternalstore internally this be the same symptom that folk be hit in but I m not sure whether the cause be the same for everyone there how often do this bug happen every time devtool package automate no response devtool version automate no response error message automate no response error call stack automate no response error component stack automate no response github query string automate no response |
facebookreact | devtool bug command phasescriptexecution fail with a nonzero exit code | Bug | website or app command phasescriptexecution fail with a nonzero exit code repro step show error command phasescriptexecution fail with a nonzero exit code when I be try to play the ios project from a m2 chip macbook pro it be work fine in intel chip show error when try to play from vscode the follow build command fail phasescriptexecution cp user generate spec user safwan library developer xcode deriveddata skizzlehr aqdqtsvzpusqzbchycwsluqghbka build intermediate noindex pod build debug iphonesimulator react rncore build script 46eb2e00025130 sh in target react rncore from project pod 1 failure how often do this bug happen every time devtool package automate no response devtool version automate no response error message automate no response error call stack automate no response error component stack automate no response github query string automate no response |
facebookreact | devtool bug jsxdev be not a function | Bug | website or app repro step I have deploy my website on render render host platform show I successful deploy but I be not able see anything can anyone guide I how often do this bug happen every time devtool package automate no response devtool version automate no response error message automate no response error call stack automate no response error component stack automate no response github query string automate no response |
facebookreact | devtool bug could not find node with i d 155 in commit tree | Bug | website or app chrome repro step I be work on a development task after log in to an internal website I click inspect to open the developer tool in chrome and select profiler next I click start profile and refresh the page after everything be render I stop profile when read the profile datum by click the component and the time it be render this exception be throw from time to time I try to refresh the frame but this didn t help at all how often do this bug happen often devtool package automate react devtool extension devtool version automate 5 0 0 993c4d003 error message automate could not find node with i d 155 in commit tree error call stack automate text at chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 1 1118876 at map foreach at chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 1 1118825 at rr getrankedchartdata chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 1 1119305 at commitrankedautosizer chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 1 1355868 at lf chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 1 40670 at gh chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 1 61725 at yn chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 1 118951 at rk chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 1 103877 at qk chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 1 103805 error component stack automate text at commitrankedautosizer chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 1 1355625 at div at div at div at settingsmodalcontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 1 1253868 at chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 1 1484419 at bo chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 1 1271707 at div at div at themeprovider chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 1 1274418 at chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 1 1274615 at div at div at div at themeprovider chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 1 1274418 at timelinecontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 1 1344475 at profilercontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 1 1336084 at treecontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 1 1166113 at settingscontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 1 1194207 at modaldialogcontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 1 1278876 at devtool devtool chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 1 1492154 github query string automate text not find node with i d in commit tree in title be issue be open be public label component developer tool repo facebook react |
facebookreact | devtool bug can not add node 295 because a node with that i d be already in the store | Bug | website or app oftp app repro step the error be throw at at ee emit at at at array foreach at am onmessage how often do this bug happen every time devtool package automate react devtool core devtool version automate 4 27 2 7f747b80e error message automate can not add node 295 because a node with that i d be already in the store error call stack automate text at at ee emit at at at array foreach at am onmessage error component stack automate no response github query string automate text add node because a node with that i d be already in the store in title be issue be open be public label component developer tool repo facebook react |
facebookreact | devtool bug recent version break modal in chrome browser | Bug | website or app na repro step create reproduction environment 1 create sample modal view 2 inside modal do some operation open signin signup url step to reproduce on click of button modal open up actual behaviour modal view close abruptly user sign in detail be not take expect behaviour modal view should stay up to ask for sign in detail this issue be happen on recent react dev tool update on chrome browser could you please help fix this how often do this bug happen often devtool package automate no response devtool version automate no response error message automate no response error call stack automate no response error component stack automate no response github query string automate no response |
facebookreact | devtool bug can not remove node 434 because no matching node be find in the store | Bug | website or app localhost repro step 1 log to admin panel 2 go to user info how often do this bug happen every time devtool package automate react devtool extension devtool version automate 4 28 5 ef8a840bd error message automate can not remove node 434 because no matching node be find in the store error call stack automate text at chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 1 1126778 at a emit chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 1 1095954 at chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 1 1097642 at bridgelisten chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 1 1495532 error component stack automate no response github query string automate text remove node because no matching node be find in the store in title be issue be open be public label component developer tool repo facebook react |
facebookreact | devtool bug getcommittree invalid commit 13 for root 1 there be only 7 commit | Bug | website or app react dev tool repro step react dev tool error how often do this bug happen sometimes devtool package automate react devtool core devtool version automate 4 28 5 ef8a840bd error message automate getcommittree invalid commit 13 for root 1 there be only 7 commit error call stack automate text at qe c user pritam appdata roam npm node modules react devtool node modules react devtool core dist standalone js 2 1024138 at ar getcommittree c user pritam appdata roam npm node modules react devtool node modules react devtool core dist standalone js 2 1027306 at pc c user pritam appdata roam npm node modules react devtool node modules react devtool core dist standalone js 2 1243713 at an c user pritam appdata roam npm node modules react devtool node modules react devtool core dist standalone js 2 39841 at ii c user pritam appdata roam npm node modules react devtool node modules react devtool core dist standalone js 2 59412 at ns c user pritam appdata roam npm node modules react devtool node modules react devtool core dist standalone js 2 118054 at il c user pritam appdata roam npm node modules react devtool node modules react devtool core dist standalone js 2 101534 at rl c user pritam appdata roam npm node modules react devtool node modules react devtool core dist standalone js 2 101463 at nl c user pritam appdata roam npm node modules react devtool node modules react devtool core dist standalone js 2 101281 at sl c user pritam appdata roam npm node modules react devtool node modules react devtool core dist standalone js 2 98382 error component stack automate text at pc c user pritam appdata roam npm node modules react devtool node modules react devtool core dist standalone js 2 1243514 at div at div at div at ko c user pritam appdata roam npm node modules react devtool node modules react devtool core dist standalone js 2 1151045 at c user pritam appdata roam npm node modules react devtool node modules react devtool core dist standalone js 2 1361291 at ms c user pritam appdata roam npm node modules react devtool node modules react devtool core dist standalone js 2 1166739 at c user pritam appdata roam npm node modules react devtool node modules react devtool core dist standalone js 2 1169395 at div at div at div at ss c user pritam appdata roam npm node modules react devtool node modules react devtool core dist standalone js 2 1169229 at ic c user pritam appdata roam npm node modules react devtool node modules react devtool core dist standalone js 2 1233344 at wu c user pritam appdata roam npm node modules react devtool node modules react devtool core dist standalone js 2 1225803 at ut c user pritam appdata roam npm node modules react devtool node modules react devtool core dist standalone js 2 1073442 at jt c user pritam appdata roam npm node modules react devtool node modules react devtool core dist standalone js 2 1100719 at os c user pritam appdata roam npm node modules react devtool node modules react devtool core dist standalone js 2 1173613 at I c user pritam appdata roam npm node modules react devtool node modules react devtool core dist standalone js 2 1367821 github query string automate text invalid commit for root there be only commit in title be issue be open be public label component developer tool repo facebook react |
facebookreact | devtool bug footer next button hover ui issue | Bug | website or app repro step when hover on the next navigation button the text overflow the box issue image screenshot 2023 11 29 103122 expect image screenshot 2023 11 29 103037 code medium min width 768px md w 80 width 20rem fix code medium min width 768px md w 80 width 23rem how often do this bug happen every time devtool package automate no response devtool version automate no response error message automate no response error call stack automate no response error component stack automate no response github query string automate no response |
facebookreact | devtool bug react devtool be not there in codesandbox | Bug | website or app repro step I be follow the react dev docs I be at tic tac toe chapter and do my code stuff in codesandbox as per document I trigger an issue that react devtool be not there in code sandbox how often do this bug happen every time devtool package automate no response devtool version automate no response error message automate no response error call stack automate no response error component stack automate no response github query string automate no response |
facebookreact | devtool bug react dev tool break gstreamer doc | Bug | website or app repro step 1 enable react dev tool browser extension for chrome firefox 1 visit 1 try to scroll leave navigation panel how often do this bug happen every time devtool package automate no response devtool version automate no response error message automate no response error call stack automate no response error component stack automate no response github query string automate no response |
facebookreact | devtool bug could not find node with i d 1011 in commit tree | Bug | website or app localhost repro step uncaught error could not find node with i d 1011 in commit tree the error be throw at chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 1 1176211 at map foreach at rankedchartbuilder getchartdata chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 1 1176159 at ir getrankedchartdata chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 1 1177722 at commitrankedautosizer chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 1 1448087 at hf chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 1 40041 at ah chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 1 60898 at la chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 1 110056 at lk chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 1 104943 at kk chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 1 104082 the error occur at commitrankedautosizer chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 1 1447829 at div at div at div at settingsmodalcontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 1 1339271 at profiler profiler chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 1 1581281 at ql chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 1 1359803 at div at div at themeprovider chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 1 1362652 at portaledcontent chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 1 1362853 at div at div at div at themeprovider chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 1 1362652 at timelinecontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 1 1435825 at profilercontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 1 1426912 at treecontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 1 1247943 at settingscontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 1 1272935 at modaldialogcontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 1 1367483 at devtool devtool chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 1 1589837 how often do this bug happen every time devtool package automate react devtool extension devtool version automate 4 28 4 5eda682f8 error message automate could not find node with i d 1011 in commit tree error call stack automate text at chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 1 1176211 at map foreach at rankedchartbuilder getchartdata chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 1 1176159 at ir getrankedchartdata chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 1 1177722 at commitrankedautosizer chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 1 1448087 at hf chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 1 40041 at ah chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 1 60898 at la chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 1 110056 at lk chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 1 104943 at kk chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 1 104082 error component stack automate text at commitrankedautosizer chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 1 1447829 at div at div at div at settingsmodalcontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 1 1339271 at profiler profiler chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 1 1581281 at ql chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 1 1359803 at div at div at themeprovider chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 1 1362652 at portaledcontent chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 1 1362853 at div at div at div at themeprovider chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 1 1362652 at timelinecontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 1 1435825 at profilercontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 1 1426912 at treecontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 1 1247943 at settingscontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 1 1272935 at modaldialogcontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 1 1367483 at devtool devtool chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 1 1589837 github query string automate text not find node with i d in commit tree in title be issue be open be public label component developer tool repo facebook react |
facebookreact | devtool bug can not add node 1 because a node with that i d be already in the store | Bug | website or app devtool bug can not add node 1 because a node with that i d be already in the store repro step devtool bug can not add node 1 because a node with that i d be already in the store how often do this bug happen every time devtool package automate react devtool extension devtool version automate 4 28 4 5eda682f8 error message automate can not add node 1 because a node with that i d be already in the store error call stack automate text at chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 1 1186277 at c emit chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 1 1143218 at chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 1 1144967 at bridgelisten chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 1 1599236 error component stack automate text devtool bug can not add node 1 because a node with that i d be already in the store github query string automate text add node because a node with that i d be already in the store in title be issue be open be public label component developer tool repo facebook react |
facebookreact | devtool bug can not add node 1 because a node with that i d be already in the store | Bug | website or app private repo can not give access to application repro step 1 run application how often do this bug happen every time devtool package automate react devtool extension devtool version automate 4 28 0 035a41c4e error message automate can not add node 1 because a node with that i d be already in the store error call stack automate text at chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 28171 41 at bridge emit chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 24827 22 at chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 24996 14 at listener chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 57406 39 error component stack automate no response github query string automate text add node because a node with that i d be already in the store in title be issue be open be public label component developer tool repo facebook react |
facebookreact | devtool bug devtool extension build fail in window and ubuntu | Bug | website or app n a repro step devtool extension be not build in ubuntu and window below be the extension build fail in ubuntu even though it say chrome extension have build bikid476 bikisdesktop react 1 package react devtool extension 8 5 2023 1 40 08 pm below be the extension fail in windows bikid476 bikisdesktop react 1 package react devtool extension 8 5 2023 1 51 08 pm it just fail with some artifact error hoxyq my mac have go dead and I be look to tinker with devtool and have some idea in plan to implement so we can fix this out and hopefully I can continue to work on devtool how often do this bug happen every time devtool package automate no response devtool version automate no response error message automate no response error call stack automate no response error component stack automate no response github query string automate no response |
facebookreact | bug 18 3 0 canary rendertostre hoist some tag to top work in 18 2 | Bug | react version 18 3 0 canary 493f72b0a 20230727 step to reproduce 1 run follow code js import as reactdomserver from react dom server const element meta and title be hoist title the script tag be not hoist but this be hoist console log reactdomserver rendertostre element link to code example the current behavior console log output title the expect behavior console log output title |
facebookreact | devtool bug devtool extension build fail in window and ubuntu | Bug | website or app n a repro step be work on react devtool extension for a while now my mac get some issue so I switch to a window machine but currently I be unable to build the react devtool extension and run it locally here be the napshot of the error window powershell 7 28 2023 10 43 05 be how often do this bug happen every time devtool package automate no response devtool version automate no response error message automate no response error call stack automate no response error component stack automate no response github query string automate no response |
facebookreact | devtool bug chrome extension get disconnect from the page after 30sec of inactivity | Bug | website or app repro step step 1 go to a react page like 2 open the devtool component tab everything work correctly 3 change tab a non react one and wait 30 sec 5 min not super exact 4 go back to the tab that have the react page you re debug 5 the component do not work anywore you can t select and view component on the page screenshot 2023 07 17 at 3 40 10 pm my guess be that it s relate to chrome kill the service worker after inactivity on the page see c185 screenshot 2023 07 17 at 3 41 13 pm go back to the page doesn t seem to wake the serviceworker up chrome version 114 0 5735 198 official build x86 64 react extension 4 28 0 macos 13 4 1 how often do this bug happen every time devtool package automate no response devtool version automate no response error message automate no response error call stack automate no response error component stack automate no response github query string automate no response |
facebookreact | devtool bug deprecate react devtool global hook | Bug | website or app repro step hi I have hear that the new version of react will not support the react devtool global hook if there any information about this update that you can share be there a new way to achieve the same result of use the react devtool global hook but with a different method what be the future of react without the react devtool global hook reactime and react inspector in the chrome store use this hook how often do this bug happen every time devtool package automate no response devtool version automate no response error message automate no response error call stack automate no response error component stack automate no response github query string automate no response |
facebookreact | devtool bug deprecate react devtool global hook | Bug | website or app n a repro step hi I have hear that the new version of react will not support the react devtool global hook if there any information about this update that you can share be there a new way to achieve the same result of use the react devtool global hook but with a different method what be the future of react without the react devtool global hook how often do this bug happen every time devtool package automate no response devtool version automate no response error message automate no response error call stack automate no response error component stack automate no response github query string automate no response |
facebookreact | devtool bug can not remove node 0 because no matching node be find in the store | Bug | website or app local repro step open react devtool how often do this bug happen every time devtool package automate react devtool core devtool version automate 4 27 8 2468a8735 error message automate can not remove node 0 because no matching node be find in the store error call stack automate text at user wangx config yarn global node modules react devtool core dist standalone js 39 338605 at f emit user wangx config yarn global node modules react devtool core dist standalone js 39 283790 at user wangx config yarn global node modules react devtool core dist standalone js 39 285331 at user wangx config yarn global node modules react devtool core dist standalone js 39 677861 at array foreach at lh e onmessage user wangx config yarn global node modules react devtool core dist standalone js 39 677845 at a t user wangx config yarn global node modules react devtool core dist standalone js 39 2836 at a emit node event 513 28 at e export f user wangx config yarn global node modules react devtool core dist standalone js 3 38972 at e export emit node event 513 28 error component stack automate no response github query string automate text remove node because no matching node be find in the store in title be issue be open be public label component developer tool repo facebook react |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.