Change Details

##Descriptive Title Typing/searching on stable budgie in Firefox 112.0.2 (flatpak or stable version) middle page's/buttom page's search box's homepage of a new private window/homepage button in private browsing, redirects to the (wrong) search address line box on the top of the browser, what which apparently should not happen. Noticed on the recent update/s but unsure it's the last one. ##Environment - Budgie 10.7.2 (Fully updated) - Shannon (Fully updated) - Intel i5-8250U (8) @ 3.400GHz - Intel UHD Graphics 620 (Integrated, no other GPU. 915i/mesa driver - shannon's updated) - Browser: Any of Firefox Flatpak 112.0.2 Flatpak 1.0, Regular Firefox 112.0.2 (Both versions installed but it was difficult to determine if issue is shown on both. I etablished it is. Search box and Address box seperated, home for private mode was the defeault search home address (duckduckgo) but without shortcuts and links.) ___ ####ADDITIONAL NON OFFICIAL/NON ORDERED INFO ADDED JUST IN CASE. - Firefox issue: Couldn't check non private window since the home page is blank there for me as it should. It happens on any new private window and while opening private window mode. Worth a check with normal window mode if one can do so.) I couldn't yet check non private window on Firefox due to having a different homepage. I couldn't yet test other DE or browsers. This, beside a different DE testing, may be done later if I can. - Possibly similar or linked (freezing/focus/capture/windowing/refresh) recent issues on Virtualbox and Steam could not be reported orderly but may be related: - Virutualbox (current, matches kernel) 7.08-254 (Only noted just in case for some potencially similar issues on that too which can't report orderly. VM restored from backup. Can't reproduce as it's intermitent but happening. Noticed before last update but was not happening before the first CDN update. Origin, nature and cause unknown. Background penetration while browsing Firefox on the VM, and the VM menu may have a windowing/capture/focus issue from inside the VM in a way which can't be orderly/exactly/accurately reported here.) Noting other person reported a VM issue, I think a background penetration issue and typing issue, but unsure. Noting there was, by a search, a fixed bug on firefox not being full opeque but it was markd as solved, and this is only a VM issue and of a newer version. - Steam: 8 experimental beta (updated) (Only noted just in case for some potencially similar issues on that too which can't report ordery. Can't reproduce as it's intermitent but happening. Steam restart or full restart was needed to restore on the last occasions remembred. I also think at times I saw the mouse cursor moving slowly in small jumps on some steam window. I couldn't well use the budgie restart extention since it didnt work and caused a similar issue with the pannel, requiring restart.) - Budgie pannels and the restart app - see steam's description above. Noting other people reported freezing on plasma. I think at least one other non orderly reported a pannel or freezing issue on stable budgie. I stopped using that app since. - Note: Most isues, beside the mainly reported firefox issue, noticed before last update but was not happening before the first CDN update and it's unclear when those appeard, and this includes the mainly reported Firefox issue which I have no idea when it introduced at all since it never bothered me and was an accidental finding. Origin, nature and cause unknown and there could even be a user error leading to instability, or malfunctioning of the machine. I subjectively think some thing went worse on last 1-3 updates though on those non orderly reported regards. There seem to be some other small recently appearing isues which I don't remember well at all. ##Expected Behavior Apparently typing on a (middle page's/buttom page's) firefox's homepage's search box (after verification that box is chosen) should keep the cursor and the text typed in the chosen searchbox and not redirect it to the browser upper search line. ##Actual Behavior Opening a new (private in the case tested) window or pressing the home button, arrriving to the default search home page of the browser and chosing the button/middle search box of that default home page, (duckduckgo without shotcuts in this case) redirects the cursor/chosen typing box from that box and perform a search from there and not from the browser's built in search box on top (seperated in this case from the address line) which is in the search address line on the top of the browser itself. Search from the default homepage's middle/center/buttom page's search box becomes impossible. I could still type on other boxes such as while login in to sites or posting. ##Steps to reproduce On budgie 10.7.2 shannon, use Firefox 112.0.2 with the default firefox home search page (installed on both flatpak and normal version in my case) with a sepeated address and search line on top, open the default search home page and choose the search box in the middle. The cursor is shown in it. Start typing in it. The cursor and the typed text suddenly appear on the search line on the top of the browser instead. This happens 100% of the time for me in the environment I described above in the environment category. ##Demonstration of bug (I Could't do that, but noting:) While I can't capture or demonstrate this, the steps to reproduce may demonstrate it easily on a given affected browser if you have a similar case, (at least if you have that version as the default, at least, and verify it's that version on the about line,) since it happens 100% of the time for me. What which may be difficult is checking both flatpak and stock Firefox versions on the same installation but I did do that myself and noticed the bug on both versions. What I didn't test yet is different browsers, non private mode, different search engine other that duckduckgo, or having some shortcuts in the default search homepage beside the search itself (Those may be tested later). Or a different DE/other environmental aspects (which I can't check)

##Descriptive Title Typing/searching on stable budgie in Firefox 112.0.2 (flatpak or stable version) middle page's/buttom page's search box's homepage of a new private window/homepage button in private browsing, redirects to the (wrong) search address line box on the top of the browser, what which apparently should not happen. Noticed on the recent update/s but unsure it's the last one. ##Environment - Budgie 10.7.2 (Fully updated) - Shannon (Fully updated) - Intel i5-8250U (8) @ 3.400GHz - Intel UHD Graphics 620 (Integrated, no other GPU. 915i/mesa driver - shannon's updated) - Browser: Any of Firefox Flatpak 112.0.2 Flatpak 1.0, Regular Firefox 112.0.2 (Both versions installed but it was difficult to determine if issue is shown on both. I etablished it is. Search box and Address box seperated, home for private mode was the defeault search home address (duckduckgo) but without shortcuts and links.) ___ ####ADDITIONAL NON OFFICIAL/NON ORDERED INFO ADDED JUST IN CASE. - Firefox issue: Couldn't check non private window since that home page is set to about:blank. It happens on any new private window and while opening private window mode. Worth a check with normal window mode if one can do so). I couldn't yet test other DE or browsers, but it seems all but the DE can be tested later. - Possibly similar or linked (freezing/focus/capture/windowing/refresh) recent issues on Virtualbox and Steam could not be reported orderly but may be related: - Virutualbox (current, matches kernel) 7.08-254 (Only noted just in case for some potentially similar issues on that too which can't report orderly. VM restored from backup. Can't reproduce as it's intermitent but happening. Noticed before last update but was not happening before the first CDN update. Origin, nature and cause unknown. Background penetration while browsing Firefox on the VM, and the VM menu may have a windowing/capture/focus issue from inside the VM in a way which can't be orderly/exactly/accurately reported here.) Noting other person reported a VM issue, I think a background penetration issue and typing issue, but unsure. Noting a search revealed a fixed bug on firefox not being full opeque. The other issue was markd as solved, and this one is only a VM issue and of a newer version. - Steam: 8 experimental beta (updated) (Only noted just in case for some potentially similar issues on that too which can't report ordery. Can't reproduce as it's intermitent but happening. Steam restart or full restart was needed to restore on the last occasions remembered. I also saw the mouse cursor moving slowly in small jumps on some steam window on some occasions. I couldn't well use the budgie restart extention app since it didnt work and caused a similar issue with the pannel, requiring restart.) - Budgie pannels and the restart app - see steam's description above. Noting other people reported freezing on plasma. I think at least one other non orderly reported a pannel or freezing issue on stable budgie. I stopped using that app since. - Note: Most isues, beside the mainly reported firefox issue, noticed before last update but was not happening before the first CDN update and it's unclear when those appeard, and this includes the mainly reported Firefox issue which I have no idea when it introduced at all since it never bothered me and was an accidental finding. Origin, nature and cause unknown and there could even be a user error leading to instability, or malfunctioning of the machine. I subjectively think some thing went worse on last 1-3 updates though on those non orderly reported regards. There seem to be some other small recently appearing isues which I don't remember well at all. ##Expected Behavior Apparently typing on a (middle page's/buttom page's) firefox's homepage's search box (after verification that box is chosen) should keep the cursor and the text typed in the chosen searchbox and not redirect it to the browser upper search line. ##Actual Behavior Opening a new (private in the case tested) window or pressing the home button, arrriving to the default search home page of the browser and chosing the button/middle search box of that default home page, (duckduckgo without shotcuts in this case) redirects the cursor/selected typing box from that box and perform a search from there and not from the browser's built in search box on top (seperated in this case from the address line) which is in the search address line on the top of the browser itself. Searching from the default homepage's middle/center/buttom page's search box becomes impossible. I could still type on other boxes such as while login in to sites or posting. ##Steps to reproduce On budgie 10.7.2 shannon, use Firefox 112.0.2 with the default firefox home search page (installed on both flatpak and normal version in my case) with a sepeated address and search line on top, open the default search home page and choose the search box in the middle. The cursor is shown in it. Start typing in it. The cursor and the typed text suddenly appear on the search line on the top of the browser instead. This happens 100% of the time for me in the environment I described above in the environment category. ##Demonstration of bug (I Could't do that, but noting:) While I can't capture or demonstrate this, the steps to reproduce may demonstrate it easily on a given affected browser if you have a similar case, (at least if you have that version as the default, at least, and verify it's that version on the about line,) since it happens 100% of the time for me. What which may be difficult is checking both flatpak and stock Firefox versions on the same installation but I did do that myself and noticed the bug on both versions. What I didn't test yet is different browsers, non private mode, different search engine other that duckduckgo, or having some shortcuts in the default search homepage beside the search itself (Those may be tested later). Or a different DE/other environmental aspects (which I can't check)

##Descriptive Title Typing/searching on stable budgie in Firefox 112.0.2 (flatpak or stable version) middle page's/buttom page's search box's homepage of a new private window/homepage button in private browsing, redirects to the (wrong) search address line box on the top of the browser, what which apparently should not happen. Noticed on the recent update/s but unsure it's the last one. ##Environment - Budgie 10.7.2 (Fully updated) - Shannon (Fully updated) - Intel i5-8250U (8) @ 3.400GHz - Intel UHD Graphics 620 (Integrated, no other GPU. 915i/mesa driver - shannon's updated) - Browser: Any of Firefox Flatpak 112.0.2 Flatpak 1.0, Regular Firefox 112.0.2 (Both versions installed but it was difficult to determine if issue is shown on both. I etablished it is. Search box and Address box seperated, home for private mode was the defeault search home address (duckduckgo) but without shortcuts and links.) ___ ####ADDITIONAL NON OFFICIAL/NON ORDERED INFO ADDED JUST IN CASE. - Firefox issue: Couldn't check non private window since thethat home page is blank there for me as it shouldset to about:blank. It happens on any new private window and while opening private window mode. Worth a check with normal window mode if one can do so.) I couldn't yet check non private window on Firefox due to having a different homepage. I couldn't yet test other DE or browsers. This,Worth a check with normal window mode if one can do so). beside a different DE testingI couldn't yet test other DE or browsers, may be done later if I canbut it seems all but the DE can be tested later. - Possibly similar or linked (freezing/focus/capture/windowing/refresh) recent issues on Virtualbox and Steam could not be reported orderly but may be related: - Virutualbox (current, matches kernel) 7.08-254 (Only noted just in case for some potenctially similar issues on that too which can't report orderly. VM restored from backup. Can't reproduce as it's intermitent but happening. Noticed before last update but was not happening before the first CDN update. Origin, nature and cause unknown. Background penetration while browsing Firefox on the VM, and the VM menu may have a windowing/capture/focus issue from inside the VM in a way which can't be orderly/exactly/accurately reported here.) Noting other person reported a VM issue, I think a background penetration issue and typing issue, but unsure. Noting there was, byNoting a search, revealed a fixed bug on firefox not being full opeque. a fixed bug on firefox not being full opeque but itThe other issue was markd as solved, and this one is only a VM issue and of a newer version. - Steam: 8 experimental beta (updated) (Only noted just in case for some potenctially similar issues on that too which can't report ordery. Can't reproduce as it's intermitent but happening. Steam restart or full restart was needed to restore on the last occasions remembered. I also think at times I saw the mouse cursor moving slowly in small jumps on some steam window on some occasions. I couldn't well use the budgie restart extention app since it didnt work and caused a similar issue with the pannel, requiring restart.) - Budgie pannels and the restart app - see steam's description above. Noting other people reported freezing on plasma. I think at least one other non orderly reported a pannel or freezing issue on stable budgie. I stopped using that app since. - Note: Most isues, beside the mainly reported firefox issue, noticed before last update but was not happening before the first CDN update and it's unclear when those appeard, and this includes the mainly reported Firefox issue which I have no idea when it introduced at all since it never bothered me and was an accidental finding. Origin, nature and cause unknown and there could even be a user error leading to instability, or malfunctioning of the machine. I subjectively think some thing went worse on last 1-3 updates though on those non orderly reported regards. There seem to be some other small recently appearing isues which I don't remember well at all. ##Expected Behavior Apparently typing on a (middle page's/buttom page's) firefox's homepage's search box (after verification that box is chosen) should keep the cursor and the text typed in the chosen searchbox and not redirect it to the browser upper search line. ##Actual Behavior Opening a new (private in the case tested) window or pressing the home button, arrriving to the default search home page of the browser and chosing the button/middle search box of that default home page, (duckduckgo without shotcuts in this case) redirects the cursor/chosenselected typing box from that box and perform a search from there and not from the browser's built in search box on top (seperated in this case from the address line) which is in the search address line on the top of the browser itself. Searching from the default homepage's middle/center/buttom page's search box becomes impossible. I could still type on other boxes such as while login in to sites or posting. ##Steps to reproduce On budgie 10.7.2 shannon, use Firefox 112.0.2 with the default firefox home search page (installed on both flatpak and normal version in my case) with a sepeated address and search line on top, open the default search home page and choose the search box in the middle. The cursor is shown in it. Start typing in it. The cursor and the typed text suddenly appear on the search line on the top of the browser instead. This happens 100% of the time for me in the environment I described above in the environment category. ##Demonstration of bug (I Could't do that, but noting:) While I can't capture or demonstrate this, the steps to reproduce may demonstrate it easily on a given affected browser if you have a similar case, (at least if you have that version as the default, at least, and verify it's that version on the about line,) since it happens 100% of the time for me. What which may be difficult is checking both flatpak and stock Firefox versions on the same installation but I did do that myself and noticed the bug on both versions. What I didn't test yet is different browsers, non private mode, different search engine other that duckduckgo, or having some shortcuts in the default search homepage beside the search itself (Those may be tested later). Or a different DE/other environmental aspects (which I can't check)