This document provides instructions for using the Torque Clientless program for Silkroad Online. It outlines the main functions on the main tab including logging in with an alias, entering login information, viewing character stats, and switching to a game client. It also describes settings that can be configured for characters like adding masters, raising masteries, and allocating stat points. Additional tabs are outlined for chat functions and viewing server stats. A character creator section provides options for making new characters.
This document provides step-by-step instructions for getting started with WordPress, including setting up a blog and making a sample post. It compares WordPress to Blogger and discusses their features, typical users, costs, and ease of use to help determine which platform is best. Contact information is also provided for further WordPress help.
1. The document describes the premium features of the Inspire 8 theme for XOOPS, including an integrated Superfish menu, lazy loading of images, and an integrated slideshow.
2. It highlights how the Superfish menu is customized to add user menu, search box, and login box and is fully integrated with XOOPS modules.
3. Additional premium features include CSS3 properties, avoiding repeat loading of jQuery, compatibility with XOOPS 2.4.5, and minor fixes.
Premium prescription lens configuration Magento 2 extension turns your digital lens store into an online place where your customers can easily purchase the lenses prescribed to them.
O documento discute a história da matemática ao longo dos tempos, mencionando os sistemas numéricos romano, egípcio, grego, maia e árabe. Os egípcios foram pioneiros no campo da matemática antiga, enquanto os gregos buscavam compreender o lugar do homem no universo de forma racional. Os maias utilizaram um sistema vigesimal e estabeleceram as datas mais antigas da história da humanidade por meio de símbolos figurativos. O sistema numérico decimal árabe, com
Falkland Oil and Gas is the largest license holder in the Falkland Islands with interests in over 40,000 km2. They plan a five well drilling program in 2015 targeting over 1.4 billion barrels of gross unrisked prospective resources. The first well, Zebedee, will test prospects in the North Falkland Basin in March 2015. Subsequent wells will target large fans and fault blocks in the South and East basins, beginning with the Humpback prospect in the Diomedea Fan Complex in Q3 2015. Falkland Oil and Gas has identified multiple follow-on prospects across its licenses contingent on the results of the 2015 drilling program.
Hundreds of Firefox addons are created every week. Millions of users download them. Some addons are even recommended by the Mozilla community, and users implicitly trust them. We don't trust a single one, and we will show you why.
This talk details how we have abused some of the most popular and recommended Firefox addons, with previously unreleased vulnerabilities. From the Mozilla download statistics, over 15 million users are potentially affected. Demos will cover remote code execution, local file disclosure and other tailored Firefox Addon exploits.
Don't panic - the Addons manager can be found under the 'Tools' tab in your Firefox menu. We expect to see a lot of people clicking the "Uninstall" button after this presentation.
Abusing, Exploiting and Pwning with Firefox Add-onsAjin Abraham
The paper is about abusing and exploiting Firefox add-on Security model and explains how JavaScript functions, XPCOM and XPConnect interfaces, technologies like CORS and WebSocket, Session storing and full privilege execution can be abused by a hacker for malicious purposes. The widely popular browser add-ons can be targeted by hackers to implement new malicious attack vectors resulting in confidential data theft and full system compromise. This paper is supported by proof of concept add-ons which abuse and exploits the add-on coding in Firefox 17, the release which Mozilla boasts to have a more secure architecture against malicious plugins and add-ons. The proof of concept includes the implementation of a Local keylogger, a Remote keylogger, stealing Linux password files, spawning a Reverse Shell, stealing the authenticated Firefox session data, and Remote DDoS attack. All of these attack vectors are fully undetectable against anti-virus solutions and can bypass protection mechanisms.
This document discusses browser add-ons and how they can improve testing efficiency. It describes browser add-ons as software extensions that add functionality to web browsers. Three add-ons are highlighted that improve testing: Responsive Web Design Tester tests websites on different screen sizes; W3Techs displays the technologies used by websites with a click; and Form Filler speeds up filling forms by auto-filling fields or bulk entry of test data. The document advocates for browser add-ons to enhance testing capabilities and productivity.
The document discusses several Firefox extensions for web developers, including NoScript which enhances security by blocking scripts, IE View Lite and Chrome View which allow testing sites in different browsers, CSS Viewer for inspecting CSS rules, and the Web Developer Toolbar which provides tools for debugging, page info, and more. The extensions are demonstrated and links provided for each one.
Web browser extensions allow custom programs to extend browser functionality. Major browsers like Chrome, Firefox, Internet Explorer, Opera, and Safari support extensions through different development approaches. Extensions are typically built with HTML, CSS, and JavaScript and add features like new pages, buttons or menus. The document outlines the file structures, guidelines and development processes for extensions in each browser. Firefox has the most complex process while Chrome and Safari aim to simplify development.
The document provides information about PC operations and browsers. It discusses the acronym PEC, strengths and skills to develop. It also discusses safety precautions for laboratories. It then discusses browsers like Internet Explorer and defines what a browser is. It explains how browsers connect to the internet, load pages, and additional resources. It lists commonly used browsers like Chrome, Firefox, Safari, and Edge. It discusses differences between browsers in user experience, home screen design, apps/plugins, rendering engines, and performance. Finally, it defines terms related to the basic browser homepage like the address bar, navigation buttons, refresh button, new tab button, bookmarks, and search and close buttons.
This document discusses Firefox extensions and customizations that can enhance the browsing experience. It provides over 20 extension recommendations in different categories like productivity, translation, bookmarks, and more. Instructions are given on how to find, install, and manage extensions in Firefox to customize the browser. Themes are also mentioned as a way to change the visual appearance of Firefox.
1) The document discusses the history of web browsers and the "Browser Wars" between Netscape and Internet Explorer. It also discusses the rise of Firefox and how Mozilla aimed to make the Internet a better place.
2) Firefox allows extensions to extend its functionality. Extensions can range from simple single-feature extensions to more complex applications. The interface of Firefox is written in XUL, which is similar to HTML and XML.
3) Developing extensions involves setting up an environment, studying existing code, debugging through trial and error. It also requires dealing with bugs and restrictions. The process can be difficult but rewarding.
The document discusses Mozilla Firefox, an open-source web browser. It notes that Firefox was created by Dave Hyatt and Blake Ross as an experimental branch of the Mozilla browser. Firefox 1.0 was released in 2004 and saw over 100 million downloads in under a year. The document outlines several features of Firefox including its speed, security, customization options through extensions and addons, and private browsing mode. It also discusses some criticisms of Firefox such as occasional crashes, slow initial startup time, and high memory usage.
Introduction to Web Browser Extension/Add-onsPranav Gupta
An overview of what Browser Extensions are, why they are useful and important, what all they can do and moreover, what kind of technologies and knowledge is involved in developing a Google Chrome Extension or Mozilla Firefox Add-on
Browser extensions, sometimes referred to as plug-ins or add-ons, are tiny pieces of software that enhances one's Web browsing experience. If you can think of a common computing task, then a browser extension has probably already been written to more easily accomplish it. Although browser extensions are written for all major Web browsers, Chad Mairn will highlight how to find and install useful extensions on Chrome and Firefox browsers. Safari and Internet Explorer users don't fear because Chad Mairn will highlight a few great extensions there as well.
Mozcafe@bcrec is a document about Mozilla, a non-profit organization dedicated to promoting an open web. It discusses Mozilla's mission to promote openness, innovation, and opportunity on the web. It also summarizes some of Mozilla's key products like Firefox, Firefox OS, and Thunderbird, as well as tools for developers. The document encourages readers to get involved by helping users, testing software, coding, translating, or doing other tasks.
Chrome extensions allow users to modify and customize their browser behavior through additional programs that can be installed from the Chrome Web Store. Extensions are built with web technologies like HTML, CSS, and JavaScript and have access to the Chrome API which allows them to interact with browser features and windows. The document provides examples of common extensions and outlines the basic skills and resources needed to develop browser extensions for Chrome.
OLLI Workshop: Browser Tips And Plug Ins May 2009sheila lafferty
This document provides an overview of the Firefox web browser and some tips for customizing it. Firefox is an open source browser that has gained popularity as an alternative to Internet Explorer. The document discusses Firefox features like tabbed browsing, add-ons, bookmarks, and privacy settings. It also provides instructions for installing Firefox, migrating bookmarks from other browsers, and installing common extensions like Adblock Plus to enhance functionality.
This document discusses how to develop browser extensions. It begins by defining a browser extension as a plugin that extends the functionality of a web browser. It then covers the basic architecture of extensions, including the manifest file, browser and page actions, content scripts, background pages, and permissions. The document provides advantages of extensions such as ease of use and support for modern technologies. It also includes a demo of building an extension using technologies like React, Redux, and Express.
The document summarizes the history of Mozilla and Firefox, from the initial open sourcing of the Netscape browser code in 1998 to the present. It discusses key milestones like the releases of Mozilla 1.0 and Firefox 1.0, and how Firefox was developed in response to limitations in Netscape and Internet Explorer. It also outlines Mozilla's vision for an open web and how the non-profit organization and browser development community operates.
The document discusses various aspects of web testing including:
1) Features that make websites complex such as customizable layouts, dynamic content, and compatibility with different browsers and devices.
2) The basics of web testing including treating each page as a "black box" and creating a state table to map connections between pages.
3) Elements to test on web pages including text, hyperlinks, graphics, forms, and other features; and ensuring proper loading, sizing, and functionality across different browsers, versions, and devices.
Mozilla is developing Firefox for mobile browsers to bring the Firefox experience to smartphones and tablets. The mobile version of Firefox will sync bookmarks, passwords and open tabs across devices using Weave Sync. It will include the Awesome Bar, tabbed browsing, add-ons and the same browser engine as desktop Firefox for a familiar experience on mobile. Mozilla aims to reduce development time for mobile apps by providing a standards-based platform through HTML5 support on mobile Firefox. An initial beta version of Firefox for smartphones running the Maemo operating system will be available, with future plans including versions for Windows Mobile and Android.
User Story Mapping - WHY and HOW, a handson workshopbhumika2108
* What is the philosophy behind story mapping, why we do it?
* Understand how to effectively story map is a crucial capability for an agile team
* Helps teams learn collaboration, share and prioritise quickly and efficiently.
How many times do we test the same things at multiple layers, multiple levels, adding time to the build process and testing cycle, delaying the feedback? We know what to test and how to test, but what is the right place to test it? Using a case study, we will see how each component can be tested and bring all these tests together to understand and build the testing pyramid and how it enables us to build the right testing framework with fewer selenium i.e functional tests.
Hundreds of Firefox addons are created every week. Millions of users download them. Some addons are even recommended by the Mozilla community, and users implicitly trust them. We don't trust a single one, and we will show you why.
This talk details how we have abused some of the most popular and recommended Firefox addons, with previously unreleased vulnerabilities. From the Mozilla download statistics, over 15 million users are potentially affected. Demos will cover remote code execution, local file disclosure and other tailored Firefox Addon exploits.
Don't panic - the Addons manager can be found under the 'Tools' tab in your Firefox menu. We expect to see a lot of people clicking the "Uninstall" button after this presentation.
Abusing, Exploiting and Pwning with Firefox Add-onsAjin Abraham
The paper is about abusing and exploiting Firefox add-on Security model and explains how JavaScript functions, XPCOM and XPConnect interfaces, technologies like CORS and WebSocket, Session storing and full privilege execution can be abused by a hacker for malicious purposes. The widely popular browser add-ons can be targeted by hackers to implement new malicious attack vectors resulting in confidential data theft and full system compromise. This paper is supported by proof of concept add-ons which abuse and exploits the add-on coding in Firefox 17, the release which Mozilla boasts to have a more secure architecture against malicious plugins and add-ons. The proof of concept includes the implementation of a Local keylogger, a Remote keylogger, stealing Linux password files, spawning a Reverse Shell, stealing the authenticated Firefox session data, and Remote DDoS attack. All of these attack vectors are fully undetectable against anti-virus solutions and can bypass protection mechanisms.
This document discusses browser add-ons and how they can improve testing efficiency. It describes browser add-ons as software extensions that add functionality to web browsers. Three add-ons are highlighted that improve testing: Responsive Web Design Tester tests websites on different screen sizes; W3Techs displays the technologies used by websites with a click; and Form Filler speeds up filling forms by auto-filling fields or bulk entry of test data. The document advocates for browser add-ons to enhance testing capabilities and productivity.
The document discusses several Firefox extensions for web developers, including NoScript which enhances security by blocking scripts, IE View Lite and Chrome View which allow testing sites in different browsers, CSS Viewer for inspecting CSS rules, and the Web Developer Toolbar which provides tools for debugging, page info, and more. The extensions are demonstrated and links provided for each one.
Web browser extensions allow custom programs to extend browser functionality. Major browsers like Chrome, Firefox, Internet Explorer, Opera, and Safari support extensions through different development approaches. Extensions are typically built with HTML, CSS, and JavaScript and add features like new pages, buttons or menus. The document outlines the file structures, guidelines and development processes for extensions in each browser. Firefox has the most complex process while Chrome and Safari aim to simplify development.
The document provides information about PC operations and browsers. It discusses the acronym PEC, strengths and skills to develop. It also discusses safety precautions for laboratories. It then discusses browsers like Internet Explorer and defines what a browser is. It explains how browsers connect to the internet, load pages, and additional resources. It lists commonly used browsers like Chrome, Firefox, Safari, and Edge. It discusses differences between browsers in user experience, home screen design, apps/plugins, rendering engines, and performance. Finally, it defines terms related to the basic browser homepage like the address bar, navigation buttons, refresh button, new tab button, bookmarks, and search and close buttons.
This document discusses Firefox extensions and customizations that can enhance the browsing experience. It provides over 20 extension recommendations in different categories like productivity, translation, bookmarks, and more. Instructions are given on how to find, install, and manage extensions in Firefox to customize the browser. Themes are also mentioned as a way to change the visual appearance of Firefox.
1) The document discusses the history of web browsers and the "Browser Wars" between Netscape and Internet Explorer. It also discusses the rise of Firefox and how Mozilla aimed to make the Internet a better place.
2) Firefox allows extensions to extend its functionality. Extensions can range from simple single-feature extensions to more complex applications. The interface of Firefox is written in XUL, which is similar to HTML and XML.
3) Developing extensions involves setting up an environment, studying existing code, debugging through trial and error. It also requires dealing with bugs and restrictions. The process can be difficult but rewarding.
The document discusses Mozilla Firefox, an open-source web browser. It notes that Firefox was created by Dave Hyatt and Blake Ross as an experimental branch of the Mozilla browser. Firefox 1.0 was released in 2004 and saw over 100 million downloads in under a year. The document outlines several features of Firefox including its speed, security, customization options through extensions and addons, and private browsing mode. It also discusses some criticisms of Firefox such as occasional crashes, slow initial startup time, and high memory usage.
Introduction to Web Browser Extension/Add-onsPranav Gupta
An overview of what Browser Extensions are, why they are useful and important, what all they can do and moreover, what kind of technologies and knowledge is involved in developing a Google Chrome Extension or Mozilla Firefox Add-on
Browser extensions, sometimes referred to as plug-ins or add-ons, are tiny pieces of software that enhances one's Web browsing experience. If you can think of a common computing task, then a browser extension has probably already been written to more easily accomplish it. Although browser extensions are written for all major Web browsers, Chad Mairn will highlight how to find and install useful extensions on Chrome and Firefox browsers. Safari and Internet Explorer users don't fear because Chad Mairn will highlight a few great extensions there as well.
Mozcafe@bcrec is a document about Mozilla, a non-profit organization dedicated to promoting an open web. It discusses Mozilla's mission to promote openness, innovation, and opportunity on the web. It also summarizes some of Mozilla's key products like Firefox, Firefox OS, and Thunderbird, as well as tools for developers. The document encourages readers to get involved by helping users, testing software, coding, translating, or doing other tasks.
Chrome extensions allow users to modify and customize their browser behavior through additional programs that can be installed from the Chrome Web Store. Extensions are built with web technologies like HTML, CSS, and JavaScript and have access to the Chrome API which allows them to interact with browser features and windows. The document provides examples of common extensions and outlines the basic skills and resources needed to develop browser extensions for Chrome.
OLLI Workshop: Browser Tips And Plug Ins May 2009sheila lafferty
This document provides an overview of the Firefox web browser and some tips for customizing it. Firefox is an open source browser that has gained popularity as an alternative to Internet Explorer. The document discusses Firefox features like tabbed browsing, add-ons, bookmarks, and privacy settings. It also provides instructions for installing Firefox, migrating bookmarks from other browsers, and installing common extensions like Adblock Plus to enhance functionality.
This document discusses how to develop browser extensions. It begins by defining a browser extension as a plugin that extends the functionality of a web browser. It then covers the basic architecture of extensions, including the manifest file, browser and page actions, content scripts, background pages, and permissions. The document provides advantages of extensions such as ease of use and support for modern technologies. It also includes a demo of building an extension using technologies like React, Redux, and Express.
The document summarizes the history of Mozilla and Firefox, from the initial open sourcing of the Netscape browser code in 1998 to the present. It discusses key milestones like the releases of Mozilla 1.0 and Firefox 1.0, and how Firefox was developed in response to limitations in Netscape and Internet Explorer. It also outlines Mozilla's vision for an open web and how the non-profit organization and browser development community operates.
The document discusses various aspects of web testing including:
1) Features that make websites complex such as customizable layouts, dynamic content, and compatibility with different browsers and devices.
2) The basics of web testing including treating each page as a "black box" and creating a state table to map connections between pages.
3) Elements to test on web pages including text, hyperlinks, graphics, forms, and other features; and ensuring proper loading, sizing, and functionality across different browsers, versions, and devices.
Mozilla is developing Firefox for mobile browsers to bring the Firefox experience to smartphones and tablets. The mobile version of Firefox will sync bookmarks, passwords and open tabs across devices using Weave Sync. It will include the Awesome Bar, tabbed browsing, add-ons and the same browser engine as desktop Firefox for a familiar experience on mobile. Mozilla aims to reduce development time for mobile apps by providing a standards-based platform through HTML5 support on mobile Firefox. An initial beta version of Firefox for smartphones running the Maemo operating system will be available, with future plans including versions for Windows Mobile and Android.
User Story Mapping - WHY and HOW, a handson workshopbhumika2108
* What is the philosophy behind story mapping, why we do it?
* Understand how to effectively story map is a crucial capability for an agile team
* Helps teams learn collaboration, share and prioritise quickly and efficiently.
How many times do we test the same things at multiple layers, multiple levels, adding time to the build process and testing cycle, delaying the feedback? We know what to test and how to test, but what is the right place to test it? Using a case study, we will see how each component can be tested and bring all these tests together to understand and build the testing pyramid and how it enables us to build the right testing framework with fewer selenium i.e functional tests.
In a team which is developing mobile apps for multiple platforms, it becomes extremely difficult to maintain multiple Automation codebases and frameworks to test the app. This becomes a bigger problem when the same team is churning out multiple flavours of the same app.
What this showcases is how we have built an automation framework that tests 2 different flavours of an app along with using the same framework to test these apps across 3 different platforms.
The session will also include the challenges we faced while moving from a purely Functional approach to writing code to an Object-oriented approach to structure our automation code.
This will help other testing practitioners attending this session in building a robust automation framework with a very reliable and scalable codebase that can be extended beyond just one application/platform.
How many times do we test the same things at multiple layers, multiple levels, adding time to the build process and testing cycle? As a result, delaying the feedback.
In this workshop, we will demonstrate how as QAs we can identify what tests can be classified as unit tests, integration test and functional test.
Using a case study, we will see how each component can be tested as part of unit testing; the integration of different parts and the functioning of the automobile as a whole and how functional tests fit into this big picture. We will then bring all these tests together to understand and build the testing pyramid.
Wearables are the next "In" thing. This talk intends to discuss the different things to watch out for while testing mobiles apps in conjunction with wearable devices like Android Wear & Apple Watch.
Reliable and fast security audits - The modern and offensive way-Mohan Gandhibhumika2108
The document discusses web application security testing. It introduces web application penetration testing and the OWASP Top 10 security vulnerabilities like injection and XSS. It provides examples of SQL injection vulnerabilities and how to exploit URLs. It discusses how to prevent these vulnerabilities through input validation, output encoding and using parameterized queries. It also covers session management vulnerabilities and the importance of authentication and authorization for application resources.
Did you check the UX Quality?-Rajarshi Raybhumika2108
The document discusses user experience (UX) quality and heuristics. It lists 10 usability heuristics for designing intuitive user interfaces, such as having the system status be visible, using language familiar to users, allowing undo and redo functions, minimizing memory load, and helping users recover from errors. The document emphasizes the importance of UX and provides questions for feedback on how to further improve UX.
QAing INFRASTRUCTURE- A QA's role in the DevOps World-Aroj P George & Harshad...bhumika2108
This document discusses the importance of infrastructure testing for QA in a DevOps environment. It outlines the differences between typical development and production infrastructures, and provides examples of what aspects of infrastructure QA should test, including database failure scenarios, application performance, server or service availability, logging and archiving, errors, resource usage, third party services, security, caching, and cross-functional requirements. It also discusses tools that can be used for infrastructure testing and debunks myths about the need for such testing.
Why did we delete our regression suite? Deepak Parmasivam & Sneha Vijayaraghavanbhumika2108
The document discusses manual testing activities including validating test failures, writing new tests, and fighting with developers. It also describes steps for validating endpoints by feeding data, simulating input, and using Stubby4J to stub responses.
Why do cars need to have the right breaking system -Shalabh Varma & Manisha A...bhumika2108
Cars need an effective braking system for safety and reliability reasons. An appropriate braking system allows the driver to slow and stop the vehicle in a controlled manner. It also provides consistency and repeatability to build confidence for the driver.
Why test automation promises more and delivers less - Deepak Koulbhumika2108
Test automation projects often fail due to having the incorrect motives of gaining brownie points rather than meeting business needs, a lack of resources that leads to asking developers or testers to take it on instead of dedicated automation engineers, and not treating automation as its own software project with proper development practices and identification of correct elements to automate.
Accessibility testing-Gyani and Siddhanthbhumika2108
This document summarizes web accessibility testing. It discusses assistive technologies like screen readers and magnifiers. It demonstrates how a screen reader works on web pages using volunteers. The document outlines accessibility guidelines and laws like WCAG 2.0 and Section 508. It discusses automated testing tools like WAVE and manual testing. Manual testing allows testing of all WCAG 2.0 success criteria and is thorough, while automated tools can only test about 50% and partially. The document concludes by welcoming questions.
This document discusses fuzz testing techniques. It describes generating random data and inputs to test systems in unexpected ways. This allows discovering bugs like hangs, crashes, and performance issues. Examples mentioned include testing a math library by generating random expressions, testing a text messaging system by simulating many parallel messages, and testing a tree parsing algorithm with huge randomly generated directory trees. Fuzz testing uncovered bugs in areas like regular expressions, logging libraries causing bottlenecks, and parsing hangs.
Why every Tester should also aspire to be a Developer on his project!-Sandee...bhumika2108
This document discusses why testers should also aspire to be developers on their projects. It notes that software development lifecycles have changed with paradigms like TDD, BDD, ATDD, and Agile requiring more multi-skilled team members. Testing is an intellectual process like coding and analysis. Understanding code helps testers take a business perspective and catch bugs earliest in development which is cheapest. Testers should own test coverage by finding untested code and having developers write tests. While testers' role is to find bugs and ensure quality, quality should be everyone's goal. Testers can better fulfill their role by understanding code more through pairing with developers, writing code, reviewing code, and helping drill
Real time trend and failure analysis using TTA-Anand Bagmar & Aasawaree Deshmukhbhumika2108
This document describes Test Trend Analyzer (TTA), a tool that provides visualizations and reports on test automation results to gauge the health of a product portfolio. TTA collects test run data, performs trend and failure analysis, and generates customizable reports. It integrates with continuous integration systems to automatically collect results and provide stakeholders with a single click view of test status.
Web android automation-Darshan Padmawarbhumika2108
This document discusses integrating web and Android device automation testing using Selenium and Robotium. It provides an overview of why such integration is useful to eliminate manual testing efforts and allow synchronous interaction and data synchronization across web and mobile platforms. It describes how Selenium supports cross-browser web testing while Robotium supports Android app testing. The integration architecture allows calling Robotium test cases from a Selenium test framework and comparing outputs. A demo and Q&A section are also included.
2. That's weird...
It works fine
on my It's never done
computer that before.
It's just some
What did you
unlucky
type in wrong
coincidence.
to get it to
crash?
3. Online community provides thousands of add-ons,
most testers do not utilize them in their testing
activity. Sometimes what you see as a defect might not
be a defect because that is something happening due
to installation of a specific add-on.
Some add-ons do not work with the latest versions of
Browsers, so you might want to have different profiles
of your browsers.
4. Firesizer - Firefox Add-on, it allows you to resize the window to
specific dimensions.
View Dependencies – Firefox Add-on, View Dependencies adds a
tab to the Page Info Window, in which it lists all the files which were
loaded to show the current page.
6. CheckFox - This add-on is helpful in checking / unchecking
multiple checkboxes in a webpage.
Auto-Reload – Chrome Extension, Reloads a web page on a regular
basis. The interval is configurable through the "options" page.
CQstyle CSS editor - Chrome Extension, Perform live CSS edits
and use a slider to quickly change values.
7. Validity - Chrome Extension, Validity can be used to quickly
validate your HTML documents from the address bar. Validity also
gives you the option to use your own installation of the W3C Validation
Service
8. WebEdit – Chrome Extension, Very fun extension, can be used to
edit any webpage!! Just press F7 on any webpage, and edit text and
delete things like photos, and embed elements. You can even delete a
YouTube video off a page!
SitezMeter - Chrome Extension, Shows the PageRank of webpages
you are browing plus site traffic charts from Google Trends, Alexa and
Compete.