Developer
  • Projects
  • Docs
  • Blog
  • Forum
  • Builds
  • BLENDER.ORG

    • Download

      Get the latest Blender, older versions, or experimental builds.

    • What's New

      Stay up-to-date with the new features in the latest Blender releases.

    LEARNING & RESOURCES

    • Blender Studio

      Access production assets and knowledge from the open movies.

    • Manual

      Documentation on the usage and features in Blender.

    DEVELOPMENT

    • Developers Blog

      Latest development updates, by Blender developers.

    • Documentation

      Guidelines, release notes and development docs.

    • Benchmark

      A platform to collect and share results of the Blender Benchmark.

    • Blender Conference

      The yearly event that brings the community together.

    DONATE

    • Development Fund

      Support core development with a monthly contribution.

    • One-time Donations

      Perform a single donation with more payment options available.

Logo
Explore
Products
Blender User Manual Developer Documentation
Blender Benchmark
Blender Studio Tools Flamenco Watchtower
Modules
Animation & Rigging Asset System Core Grease Pencil Modeling Nodes & Physics Pipeline & I/O Platforms & Builds Python API & Text Editor Sculpt, Paint & Texture Triaging User Interface VFX & Video
Rendering
Render & Cycles Viewport & EEVEE
Report a Bug Paste Code Help
Sign In
archive/phabricator
1
0
Fork 0
You've already forked phabricator
Code Issues 1 Pull Requests Packages Projects Releases Wiki Activity
Files
dd995984eba6e0a8854ef6ab9904aa3a0b8e466b
phabricator/webroot/rsrc/css/application/contentsource/content-source-view.css

8 lines
113 B
CSS
Raw Normal View History

Track content sources (email, web, conduit, mobile) for replies Summary: When an object is updated, record the content source for the update. This mostly isn't terribly useful but one concrete thing I want to do with it is let admins audit via-email replies more easily since there are a bunch of options which let you do hyjinx if you intentionally configure them insecurely. I think having a little more auditability around this feature is generally good. At some point I'm going to turn this into a link admins can click to see details. It also allows us to see how frequently different mechanisms are used, and lets you see if someone is at their desk or on a mobile or whatever, at least indirectly. The "tablet" and "mobile" sources are currently unused but I figured I'd throw them in anyway. SMS support should definitely happen at some point. Not 100% sure about the design for this, I might change it to plain text at some point. Test Plan: Updated objects and saw update sources rendered. Reviewers: jungejason, tuomaspelkonen, aran Reviewed By: jungejason CC: aran, epriestley, jungejason Differential Revision: 844
2011-08-22 10:25:45 -07:00
/**
* @provides phabricator-content-source-view-css
*/
.phabricator-content-source-view {
color: #888888;
}
Reference in New Issue Copy Permalink
Powered by Gitea Page: 119ms Template: 2ms
English
Bahasa Indonesia Deutsch English Español Français Gaeilge Italiano Latviešu Magyar nyelv Nederlands Polski Português de Portugal Português do Brasil Suomi Svenska Türkçe Čeština Ελληνικά Български Русский Українська فارسی മലയാളം 日本語 简体中文 繁體中文(台灣) 繁體中文(香港) 한국어
Licenses API