Análises para MobiDevTools
MobiDevTools por Francesco De Stefano
Análise por Jalads
Avaliado em 4 de 5
por Jalads , há 9 meses Could be better if it doesn't automatically closed when the page is reload just like the inspect elements it doesn't automatically close.
Please fix this.
Please fix this.
68 análises
- Avaliado em 3 de 5por Utilizador do Firefox 19832934 , há um dia+ displays a bunch of Dev stuff including Network, Elements & Sources.
- I don't see an option to select an element.
- When scrolling in places like Source and Application, it treats the scroll action as tap as well, so then tries to follow through when lifting the finger.
- Selecting any css or js file shows me blank space, so it's more for looks than usability. I appreciate the developer's transparency, but the extention didn't provide any usefulness past an html source viewer, and seeing how much the page is calling. - Avaliado em 1 de 5por Jacob42 , há 7 mesesWhy did you ruin the only mobile developer tools extension? You can't inspect element anymore and edit it! When you select an element, it shows a pop-up of the element, BUT YOU CAN'T EDIT IT THERE! YOU HAVE TO MANUALLY FIND IT IN THE ENTIRE HTML NOW BEFORE YOU CAN EDIT IT! Please downgrade it to old version or at least fix this issue, because I won't be using the new version until it does. I made a Mozilla account just to comment this. The app is now ruined :(
- Avaliado em 1 de 5por mimvahedi , há 7 meses
- Avaliado em 1 de 5por Utilizador do Firefox 19414562 , há 7 mesesTerrible since the update. Too minimalistic and I can't do anything, not user-friendly at all. Luckily I know how to downgrade.
- Avaliado em 1 de 5por Utilizador do Firefox 17499801 , há 7 mesesThis used to be a good extension, but the latest upgrade broke it completely for me. I had been developing some JS customization scripts for personal use, but now it’s just unusable. I don’t need a fancy interface — I need useful functionality, and several functions I relied on are gone.
I can’t even manually install an older version, since the developer removed the version history (though I’m not sure if Firefox even allows installing old versions of extensions). It’s honestly frustrating how often developers disregard users: first Mozilla made the browser worse, and now this extension has become useless. - Avaliado em 3 de 5por me , há 7 mesesThe recent update completely broke the functionality. Specifically the inspect element no longer opens the element html within the feed. Which would be ok if you actually read/ see the whole element in the element preview box. If the box at least was readable and not just one line that would be amazing
- Avaliado em 1 de 5por Mind , há 8 mesesI agree with what Byzod wrote in his review:
Please explain the reason for requesting the new permission of access my data on all websites. If it is required for new features, please provide a detailed description of what the new features are and the necessity of requesting this permission.
As it is the new permissions required are questionable.Resposta do programador
publicado a há 8 mesesThank you for your comment. I have already responded to the user you mentioned in their review with a detailed explanation regarding the permission changes. If you have any further questions or concerns, feel free to let me know.
P.S. I kindly suggest taking a moment to reflect before speaking out, as it’s easy to end up looking uninformed. The full source code of the extension is always publicly available for anyone to review. Additionally, Firefox reviewers conduct a thorough, meticulous review of every extension that surpasses 10,000 users to ensure security and compliance. We welcome scrutiny and transparency as part of our commitment to quality and user trust. - Avaliado em 5 de 5por Utilizador do Firefox 12625425 , há 8 meses
- Avaliado em 1 de 5por Byzod , há 8 mesesFirefox is prompting me that this extension is requesting new permissions: access to my data on all websites.
According to the official description, this permission means that "the extension can read the content of the websites you visit and the data you enter on web pages, including usernames and passwords.
Extensions requesting this permission may: read and write your usernames and passwords through password management services."
Before the update, the extension was already able to modify web pages to achieve all its functions without requiring this permission. Please explain the reason for requesting this new permission. If it is required for new features, please provide a detailed description of what the new features are and the necessity of requesting this permission.
Specifically, for a developer tool extension like this, standard practice is to utilize the dedicated `devtools` APIs for interaction with web pages, or at minimum, the `activeTab` permission, which only grants temporary access to the current tab when the user explicitly activates the extension. Can your extension edit inactive tab?Resposta do programador
publicado a há 8 mesesThank you for your detailed question and for raising important points about extension permissions and security — I appreciate your vigilance.
Regarding the permission to access data on all websites, this is indeed a broad permission and I want to clarify why it is necessary for this add-on’s functionality:
1. Core Functionality Requires Full Page Access:
As a developer tool, the add-on needs to interact with the full DOM and resources on any visited page, including pages not currently active in the browser. This allows features such as the foldable and editable HTML source panel, resource inspection, and network monitoring to function fully and accurately — which cannot be reliably achieved with only activeTab or limited devtools APIs.
2. Why activeTab Is Insufficient:
The activeTab permission grants temporary access only to the currently active tab when the user explicitly activates the extension. However, this add-on supports monitoring and auditing even in inactive tabs to provide seamless inspection across multiple pages — a vital capability for developers and testers working across tabs or on background tasks.
3. No Reading or Storing Sensitive Data:
While permission technically enables reading page content, this add-on does not collect, store, or transmit any personal information or user credentials. All data manipulation is strictly local to the browser session and purely for your development convenience.
4. No Use of Password Manager Interfaces:
We do not interface with password management services or attempt to read or write credentials. The warning text is a generic browser notice for this permission scope, and does not indicate actual behavior by the add-on.
5. Security and Transparency:
The add-on’s source code is fully open and available for review — https://sourceforge.net/projects/mobidevtools/. You and the community are encouraged to audit it to confirm that it operates exactly as described — securely and respectfully.
Thank you again for your thoughtful feedback. Our goal is to provide a powerful developer experience while maintaining transparency and respecting user trust. If you have further questions or suggestions on how we can improve, we are always open to constructive dialogue.
P.S. If you intend to play the expert, please be aware that the extension’s complete source code is always publicly available for download and review. While you may wish to appear an authority, it’s important to understand that this project is a genuine contribution aimed at improving developer efficiency and enhancing the prestige of the Firefox browser. Mozilla’s foundation has rightly made user privacy protection the core principle of its mission—something we fully respect and uphold in this add-on. - Avaliado em 4 de 5por Deo , há 8 mesesOMG IT'S BACK, THANK GOD YAAAAY
it's different tho, I was hoping the eruda button icons would be fixed 😔 is it possible to add an element inspector? 🥺Resposta do programador
publicado a há 8 mesesThank you so much for your excitement — it’s great to have the add-on back for you!
This version is completely rebuilt from scratch to be cleaner, lighter, and free of third-party dependencies. Regarding the Eruda icon, the design has changed, but your feedback about icons is appreciated!
Also, there is now an element inspector panel marked by a “+” icon to help with inspecting DOM elements directly. This feature will be further improved in upcoming updates to make it even more powerful and user-friendly.
We’re always open to suggestions and improvements, so keep them coming! - Avaliado em 3 de 5por Vincent9753 , há 9 mesesBetter than nothing but not really usefull. The network tab is useless. It is empty when the extension starts and the extension will disappear when you reload page. So only lengthy deferred loading will show up. I guess this is the same for js errors.
Source code has no color highlighting (listed as a feature ???) and you can't select parts of text.
Console has no code completion.
So what is left ? You can execute js on the fly and you can browse the content and cut/paste nodes. Resposta do programador
publicado a há um anoThank you so much for your kind words! I'm really glad you find MobidevTools useful. If you ever have any suggestions or feedback, I'd love to hear them!- Avaliado em 3 de 5por MRJWSS-DEV , há um ano
- Avaliado em 3 de 5por Oleg Drago , há um ano
- Avaliado em 5 de 5por Utilizador do Firefox 14809203 , há um ano
- Avaliado em 5 de 5por Utilizador do Firefox 17465280 , há um ano
Resposta do programador
publicado a há um anoThanks for pointing that out! I understand how frustrating that can be. I'll look into possible improvements to maintain console data after redirects/reloads. Appreciate your input!- Avaliado em 5 de 5por Utilizador do Firefox 15004671 , há um ano